Interop 2023: continuing to improve the web for developers
11–15 of 15 posts
Re: Interop 2023: continuing to improve the web for developers
#12I was hoping for some mention of Av1 and Avif. Av1 still isn't supported by edge and safari. And avif isn't fully supported by firefox and safari iirc (animations), and unsupported by edge. To me, these represent the most important developments in web: movimg away from JPEG and more importantly away from GIF (and no, muted mp4 is not a replacement). Would have liked JPEG-XL obviously but that doesn't seem likely anym…
Meanwhile, H.265 has been around forever and still isn't supported (well or at all) in Chrome, Firefox, or Edge.
[0]https://apps.microsoft.com/store/detail/hevc-video-extension...
Re: Interop 2023: continuing to improve the web for developers
#13How to create a general-purpose button: https://twitter.com/Steve8708/status/1620448506766045191 I feel like this should be a lot simpler than it is. Specifically, the fact that I have to create a component and rely on JS feels incredibly wrong - perhaps this is a pet peeve and isn't as bad as I am making it out to be. I hope browser vendors are able to provide a roadmap to how these types of problems can be simplifi…
The notion of wanting to make a div to be used as a button reminds me of this meme https://miro.medium.com/v2/resize:fit:4800/format:webp/1*tBk...
Re: Interop 2023: continuing to improve the web for developers
#14Re: Interop 2023: continuing to improve the web for developers
#15Earlier quoted context omitted.
The notion of wanting to make a div to be used as a button reminds me of this meme https://miro.medium.com/v2/resize:fit:4800/format:webp/1*tBk...
If browsers could let you put something in the document meta or whatever that would turn off all element styling it would be a less annoying lift to use more semantic elements. You can use resets but they’re just okay and still don’t get you to “looks exactly the same in all browsers.”