What's new in the Web (Google I/O ‘24)

This talk will cover some of the key features now included in Baseline, helping you create more beautiful and capable sites and applications.

Speaker: Rachel Andrew

Watch more:

#GoogleIO

Products Mentioned: Baseline
Event: Google I/O 2024

[dogoku]

For the love of god, please do something about scrollbar styling!

[bakerkawesa]

Great presentation. I was able to watch the whole thing despite my TikTok attention span.

[jtsimoes]

Web Platform Status will be super useful to keep track of the new features. Thank you, great resource.

[AlJey]

I can't help imagining myself watching this video in 2010. My mind would've been blown.

[tarat.techhh]

i cannot wait to remove the overlay-no-popover polyfill now!

[BauldyBoys]

Name a more iconic duo then Rachel Andrew and Sub-Grid. I'll wait.

[maxim_mazurok]

Well, that's pretty cool, but how do I keep track of the baseline required for all 2686 npm packages that my project depends on? :) I'm assuming Babel will provide some level of support similar to caniuse integration they have. But yeah, that might be a challenge for cases where feature detection doesn't work. Like if I'm constructing CSS selectors dynamically and will have :has() inside of JS string, that will be hard to detect. Probably will have to resort to runtime checks, I guess.
Also, I don't understand the value of <search> element if it's just for a11y, why not just rely on aria attribute? Or is it similar to <header> or <main> - now considered to be a vital part of any application? I kinda have a feeling that Google being a search engine wanted to assert its dominance by adding an element related to its main product :D

[dharmaturtle]

Ahhh what was that teaser about a linter/CI tooling that would tell you that you can (or can't) use a feature!? Does that exist?! EXCLAMATION POINT QUESTION MARK

[euronymoos]

Standardisation = Google speak for chromium domination so it has control as much as absolutely possible over all new “features” across the web

[Atractiondj]

The film industry once agreed to use 35mm film long ago, but you can't agree on one web standard that all browsers must follow. Instead, we wait years until we can use a new feature

[leothefieryhedgemouse]

I don't like the side tabs... plus I do not like the color picker! I want the color dropper back please!

[YordanTGeorgiev]

CSS nesting is definitely not giving anything close to easier to read completely allowing you to make a big mess 🤒

[CirTap]

Given that *<form role="search">* also creates a "search" landmark just like but with fewer characters, I don't see the advantage of using <search> at all.
This questionable fluff gets implemented instantly but other "bugs" or USEFUL features take years or decades to ship.


"They" should have made *<nobr>* official and not deprecate *<xmp>*. Both are very useful and have no simple replacement in HTML5 and cannot be emulated with CSS. Luckily they still work in all browsers but are now "invalid HTML" face-purple-crying

[mkinfrared]

Miss times when Jake was presenting new features

[SLApple-hped]

From my perspective, Google UIUX is so ugly and uncomfortable. 🙄