#caniuse — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #caniuse, aggregated by home.social.
-
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 -
-
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)
-
#Development
A framework for evaluating browser support · When is it safe to use a modern CSS feature? https://ilo.im/1613d9_____
#ModernCSS #Framework #Interoperability #BrowserSupport #Browser #Fallbacks #ProgressiveEnhancement #CanIuse #WebDev #Frontend -
#Development #Launches
caniuse-cli · A command line tool for ‘Can I use…’ and browser-compat-data https://ilo.im/1601qw_____
#BrowserSupport #CanIuse #MDN #CLI #Npm #Package #Compatibility #Browser #WebDev #Frontend -
I scratched my own itch (again) and built a #caniuse CLI tool.
It differs from other attempts at this by also integrating @MDN’s browser-compat-data + collapsing the releases in the table (just like the website does).
⌨️ npm i -g @bramus/caniuse-cli
🔗 https://github.com/bramus/caniuse-cli -
@nicolaschevobbe @jensimmons I completely agree. The `light-dark()` is right at an acceptable level of #caniuse now, too!
-
I started incorporating `@layer {}` and wow, this is very useful for theme creators, and they should start using it. Combine that with `:where()` for resets and normalise stylesheets, it gives a theme's styles as low specificity as possible.
This way, users who prefer to use a third-party theme can easily override as needed, instead of using:
* `!important`
* `.class.class.class.class`
* `:not(.\9.\9)`Another added benefit of using `@layer` is when you inspect it (F12), you can easily see where the CSS declaration came from, as it displays the `@layer`.
According to #CanIUse baseline:
> Since March 2022, this feature works across the latest devices and major browser versions
https://caniuse.com/css-cascade-layers
It should be fine to start using it, especially by theme authors and by reset/normalise projects.
What do you think?
-
#Development #Techniques
How to lazy load CodePen and CanIUse embeds · Speed up your blog post loading with a custom script https://ilo.im/15y3u6_____
#Browser #CodePen #CanIuse #LazyLoading #WebAPI #WebPerf #WebDev #Frontend #HTML #JavaScript -
*sigh* only caret-color is in #caniuse, caret-shape and caret-animation aren't. It's definitely a CSS disappointment that they aren't implemented yet.
So I'll look how to add those two there tomorrow.
Unless someone beats me to it.
-
#mdn is more up-to-date than #caniuse ?
The Iterator.prototype.reduce page has information about Edge 122, but CanIUse doesn't have anything for that version yet.
CanIUse: https://caniuse.com/mdn-javascript_builtins_iterator_reduce
-
Love all these #caniuse websites. We need more of them.
https://caniuse.com
https://www.whocanuse.com
https://www.caniemail.com -
@fugueish @dahukanna I do, but then `<input type="date">` is its own kind of jank. https://design-system.service.gov.uk/patterns/dates/ is meticulously researched. A lot of the built-ins are (or at least were) not tremendously accessible, each engine (mobile and desktop) has its own styling pecadilloes, and things don't roll into the #caniuse window with great fanfare.
-
It's time to put to rest #hex and #rgb() / #rgba() colours in #CSS and embrace the future: #oklch() and #oklab()
* oklch() model: https://caniuse.com/?search=oklch%28%29
* oklab(): https://caniuse.com/?search=oklab%28%29I'm not sure why we still need to add/support lch() and lab() since the ‘okay’ version is the ‘fixed’ version… which is better. Then again, I'm not a #colour expert, hence I can't think of a reason. (Can someone enlighten us, mortals? Thank you!)
Since oklch(), oklab(), lch(), and lab() are still not widely supported (yet), and many end-users are still using an old version of browsers without support, there is #hwb().
As you can see from https://caniuse.com/?search=hwb%28%29 hwb() is widely supported already. The only browsers still without hwb() support are niche browsers, mainly from China (they don't even support rgb() according to #CanIUse).
* Base #color model: hwb()
* To be future proof: oklch() or oklab()What I'm more excited about is the #RelativeColor feature from #CSSColor5, but that's for another day.
-
I get that browser compatibility is still a problem. But still you get pretty far with Edge. I lean on #CanIUse a lot. #WebDev #CSS #Frameworks https://caniuse.com/
