this post was submitted on 17 Mar 2024
-38 points (10.4% liked)

Firefox

17804 readers
132 users here now

A place to discuss the news and latest developments on the open-source browser Firefox

founded 4 years ago
MODERATORS
 

Everytime I want to love @firefox , I realize that it doesn't support View Transitions API ๐Ÿ˜ญ๐Ÿ˜ญ๐Ÿ˜ญ๐Ÿ˜ญ๐Ÿ˜ญ๐Ÿ˜ญ๐Ÿ˜ญ

#web #firefox #chrome #browser #javascript

you are viewing a single comment's thread
view the rest of the comments
[โ€“] [email protected] 9 points 7 months ago (2 children)
[โ€“] [email protected] 2 points 7 months ago (1 children)

Ah, I see, you posted it a few minutes before me, while I was still researching the correct link. It's funny that they declare this feature as "experimental", because it's not supported by Firefox and this document is from Mozilla. I hope they will support it soon, because this looks like a cool feature. And yes, Firefox is my favorite browser (since version 1 back in the days).

[โ€“] [email protected] 6 points 7 months ago

Also doesn't seem like it's feature complete.

The View Transitions API doesn't currently enable cross-document view transitions, but this is planned for a future level of the spec and is actively being worked on.

[โ€“] [email protected] 1 points 7 months ago (2 children)
[โ€“] [email protected] 3 points 7 months ago

Edge is chrome.

[โ€“] [email protected] 1 points 7 months ago

As the other person said, Edge is Chrome. This may sound like we're just being obtuse, but the point is that this 'standard' may only be a standard on paper so far.

Google may have (half-)written and implemented the specification, without going the full way in the standardization effort, which is to say, talk to Apple & Mozilla:

  • whether they actually want to implement it. Even if OP thinks, it's the coolest feature in the world, it means real implementation+maintenance work for Apple & Mozilla, which they might simply not be able to afford.
  • if it needs to be specified in a certain way to help Apple & Mozilla implement it. Evidently, Google didn't specify it in whole from the start either, which may very well reflect on what was easy to implement for them.