WAIT, YES! I thought I'd been tripped up by it being a pseudo-element and not a property. @keithamus.social did this get fixed along with position-try?
Posts by Firefox for Web Developers
Hah! 31 is a solid score
A very respectable score!
I tried this. It's hard.
hasUAVisualTransition landed in Firefox 149, making it available across all major engines. As well as having a very catchy name, it lets you avoid doubling up on page transitions. Here's how it works:
Interesting! In this case, I'm glad the name isn't even longer than it is.
In terms of "UA" as an initialism, you might be right, but things like the "User-Agent" header and navigator.userAgent have been around 20+ years.
If you want to experience the gross 3d transition first hand: simple-vt-demos.jakearchibald.com/gross-cube-t...
hasUAVisualTransition landed in Firefox 149, making it available across all major engines. As well as having a very catchy name, it lets you avoid doubling up on page transitions. Here's how it works:
Yeah, it seems tricky because, if you do a push navigation, escape should still do closewatcher things first. So, it's like a different layer on top of navigation. Also, the polyfill would mess with the back button.
The CloseWatcher API landed in Firefox 149, making it easy to listen for platform-specific 'dismiss' signals. Here's how it works:
Ooooo, I'm sure we can fix that… Thanks for raising it!
In terms of popover=hint, I dug into it when scripting a video, and… I can't make sense of the behaviour at all. Here's my investigation so far if you want to follow along: github.com/whatwg/html/... & github.com/whatwg/html/...
Firefox 149 is out now, and adds bunch of new web platform features, like
🎉 The CloseWatcher API
🎉 popover=hint (although I'm concerned about the spec'd behaviour)
🎉 hasUAVisualTransition on PopStateEvent
🎉 font-family: math
🎉 The CSP reporting API
And more!
developer.mozilla.org/en-US/docs/M...
There are many browsers, but only three widely-used engines. We maintain one of those engines - Gecko. Here's why we feel that browser engine diversity is essential for the future of the web blog.mozilla.org/netpolicy/20...
hah I genuinely use them. But I also use vertical tabs.
Very good!
oh no you used up all your sight!
wait is that not allowed?
But also, read the article! bsky.app/profile/keit...
Sorry everyone. You're about to spend a ton of time on this.
My score is 0.0028 💅 (although I get different scores on different screens - my best is on my MacBook)
I'll pass these on to the UX team. Thanks!
We consider the current API to be pretty bad security-wise, and are pushing for something better github.com/mozilla/stan...
JavaScript Iterator․zip landed in Firefox 148, making it simple to loop over multiple things at the same time. Here's how it works:
It is! Here's the demo random-stuff.jakearchibald.com/heart-css-sh...
It uses linear() - one of the standards I worked on.
I also built a little tool to help generate spring easings linear-easing-generator.netlify.app
The UI as before, but with no button to suggest other tabs. The entry point has been removed.
If you have blocked AI enhancements, this is the same UI - the entry point to the feature isn't there.
And of course, any already-downloaded models are deleted.
"Create tab group" UI, including a "Suggest more of my tabs" button featuring an icon typically indicating AI.
The UI when you click the button. Showing "Nightly uses AI to read your open tabs' titles and descriptions to suggest more tabs and group names. This happens on your device". There are "cancel" and "continue" buttons, along with a link to customise AI settings.
Taking, for example, the tab grouping and naming feature, if you don't "Block AI enhancements", then you're offered the feature, and if you click the button, the use of AI is explained, and you have to confirm.
If you confirm, then the local privacy-preserving model is downloaded and used.