Hacker News new | ask | show | jobs
Interop 2023: continuing to improve the web for developers (web.dev)
55 points by rnyman 1240 days ago
6 comments

I 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 anymore.

https://caniuse.com/avif

https://caniuse.com/av1

Meanwhile, H.265 has been around forever and still isn't supported (well or at all) in Chrome, Firefox, or Edge.
And rightly so. Nobody wants to pay to watch a video, not hardware makers, streaming platforms or consumers[0].

[0]https://apps.microsoft.com/store/detail/hevc-video-extension...

If you want all the details on Interop 2023 — which technologies are included and how they impact the scores — read this: https://webkit.org/blog/13706/interop-2023/
How 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 simplified someday in the future.

What part of buttons require javascript?

If you want to run javascript when a user clicks a button, yes, that will require javascript. If you want to change the default styling of buttons, you need to write some CSS. This is not 'too hard' - the video points out a single line of CSS that completely removes all default styling.

This video invents a bunch of problems, and then just solves them by just... using standard HTML elements. Links for links, buttons for buttons. The author finally ends the video with a pretty terrible recommendation of trying to hide links vs buttons to users by putting them behind the same component. Not only does this approach teach bad habbits, you can very quickly run into a bunch of different corner cases blowing up that logic even further.

The one annoying part about buttons could be how they default to type=submit, but with the web's strong focus on backwards compat, the ship sailed on that a while ago, and it's not that onerous to just put type=button on buttons you don't want to submit a form.

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.”
You don't have to create a component or rely on JS.
Excited for Colors and Subgrid. It is funny that Chrome is the laggard of those as much as people dog Safari.
Safari quite frequently has neat to CSS stuff before other browser. IIRC it had position: sticky, backdrop-filter, CSS snap points years before Chrome did.
I’m interested to know what changes are planned for Form elements!
WebAssembly integration to allow writing client side code with semantically sound languages?

No? Not interested