Post

@webdevs.firefox.com

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:

26/3/26, 2:40 pm10 reposts75 likes

Carney is a climate traitor

@jek57.bsky.social

26 Mar

I need more Jake videos like this, useful info and all the personality

Chris Haynes

@lamplightdev.com

26 Mar

This is most welcome! What would be even more welcome would be the ability to disable UA transitions too, so that we can get other browsers to behave like Firefox does here.

Jake Archibald

@jakearchibald.com

31 Mar

I found a hack! bsky.app/profile/did:...

Jake Archibald@jakearchibald.com

Folks asked if there was a way to disable Chrome's own 'back' transitions, and I didn't think there was, but… you can use a CloseWatcher to listen for the back gesture (which disables Chrome's transition), and then call location.back(). bsky.app/profile/did:...

Chris Haynes

@lamplightdev.com

31 Mar

Ah, great, thanks - I will try that out

Kaiido

@tristan-f.bsky.social

27 Mar

Isn't it the first official API exposing "UA" as a term outside of spec texts? (There is the UA-client-hints being incubated, but I don't consider it official).

Firefox for Web Developers

@webdevs.firefox.com

27 Mar

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.

Kaiido

@tristan-f.bsky.social

27 Mar

Yes I was referring to the initialism "UA". I remember I had a few complaints over some of my stackoverflow answers where I used the initialism without using the full form at all, and I think someone also complained about such use in the HTML specs, hence I now treat it as not obvious for everyone.