Every time a mastodon user uses @ instead of # and tags a Lemmy community, an angel loses its wings.
That’s OK though because we need them to stop flying around playing harps and get tf down here to fix things.
I guess they can start by giving Firefox the View Transitions API, whatever that is.
You get an upvote for “whatever that is”, because it’s annoying as hell when people post stuff with no background and assume the entire world knows what they’re crying about.
That’s why I was tongue-in-cheek mocking mastodon users who accidentally post to Lemmy. OP wasn’t trying to start conversation, they were posting a random thought into the ether.
Plus, ATCs hate angels who keep cluttering the FIR for no apparent reason. They’re not transponder equipped either.
But angels have 3 pairs of wings, so they’re fine.
I have 2 questions: Does it hurt? Does it grow?
This makes a really funny render result, at least in my client, where the sentence ends up being “Everytime I want to love, I realize that it doesn’t support View Transitions API”, which is a surreal beauty
Want to know the good news about Firefox? You can help with that.
https://developer.mozilla.org/en-US/docs/Web/API/View_Transitions_API
Seems like it’s still experimental and only supported by Chrome.
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).
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.
And edge
Edge is chrome.
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.
For anyone (like me) who didn’t know what this is: https://developer.mozilla.org/en-US/docs/Web/API/View_Transitions_API
