It sounded like a good idea to use native HTML modal `<dialog>`s for some new features, in the end even Safari has been supporting it for 4 years (and Chrome for 12 years).
Well, turns out third party components can break in various wild ways when placed in dialogs.
We spent several hours head-scratching over a broken autocomplete dropdown and a rich text editor.
Maybe it was not that a good idea in the end...
Similarly… foiled again.
Me, earlier:
Oh cool, the @ page size descriptor is supported by Chrome, Firefox and Safari! I’ll use it for this print and PDF layout that needs to be A4 landscape.
Me, now, actually trying it:
Wait, why isn’t it working? Oh. Oh no. It does not work at all in Safari. And MDN/caniuse.com say it does, but they are wrong (and there is an open issue about it).
The WebKit bug 63575 is from… 14.5 years ago.
*dies* 💀
I never gave the website favicon much thought but decided to look a bit more into it now and find it funny how Can I Use website mentions that it is a "complicated topic" in their footnotes:
#Development #Announcements
Upvote web features you need · Now on caniuse.com, web.dev, and webstatus.dev https://ilo.im/1693ku
_____
#Voting #WebFeatures #WebPlatform #Baseline #CanIuse #W3C #Browser #DevOps #WebDev #Frontend
Another great new CSS feature that is starting to be available in more browsers is field-sizing, which allows you to size an input to fit its value with:
field-sizing: content;
Great for UI like tags, where you want to be able to type directly into them and have them automatically resize to fit the text.
(#CanIUse shows the feature as not being available in Safari Technology Preview, even though all the individual child features show that it is available)
#Development #Launches
PWAscore · Compare Progressive Web App features across browsers https://ilo.im/167if0
_____
#Comparisons #CanIuse #WebApps #PWAs #Browsers #Chrome #Firefox #Safari #WebDev #Frontend
📻 Listen to @tidoust's #SoftwareEngineeringRadio podcast! As @w3c staff member, he begins by stressing the consensus-driven nature of W3C @#WebStandards. And in his role of co-chair of the Web Developer Experience (#WebDX) #CommunityGroup, François emphasizes how communication with #developers is critical, focusing on raising awareness about browser compatibility and the maturity of new features, via the baseline badges in @mdn, #caniuse and other feature catalogs.
▶️ https://se-radio.net/2025/09/se-radio-686-francois-daoust-on-w3c/
Hey #HTML / #CSS / #WebComponents folks.
If I have:
<my-fancy-component>
</my-fancy-component>
I get to target it with:
my-fancy-component {
}
right?
Does this eliminate the need for #BEM? Or is there a #CanIUse that I should be looking at for registering custom components?
(I should prototype this in a codepen but alas, no spell slots at the moment... maybe tomorrow)
Márton Salomváry
eurozerozero
Dlovan
Inautilo
W3C Developers
Erik Živković
Ricky de Laveaga
Zee