Chris Harrelson
BramusInterop 2025 is here! 馃帀
James Basoo@bramus Navigation API, just what I was hoping for! I've been finding that cross-doc VTs could really use it to unlock their full potential.
@Jbasoo Yes, it鈥檚 *SO* good.
I鈥檓 also very much looking forward to the upcoming tweaks that Chrome is working on: delayed commit (https://chromestatus.com/feature/5134734612496384) and sourceElement (https://chromestatus.com/feature/5134353390895104).
Those two additions will make the API even better than it already was.
@bramus sourceElement sounds great, I'm kind of doing something similar by tracking the click event target and using it the pageswap event.
I dont know if it's possible but I was thinking it could be handy as a pseudo-class too. That way you could do something like .card:has(:source-element) img{ view-transition-name: image; } and remove the need for pageswap JS to assign the names in some situations.
@Jbasoo Yes, and this is something I have been chatting about internally for a while now.
With .sourceElement shipping, now鈥檚 a good time for me to take this to the CSSWG.
Will file something later today :)
@bramus Amazing, I'd be keen to test any prototypes.
@Jbasoo I finally got round to filing something for this: https://github.com/w3c/csswg-drafts/issues/11801
[selectors-5] Add pseudo-class selector to target the element that initiated the outgoing navigation 路 Issue #11801 路 w3c/csswg-drafts
Intro One of the properties of the the Navigation API鈥檚 NavigateEvent is the sourceElement. From the explainer. sourceElement: An Element or null, indicating what element (if any) initiated this na...
@bramus Awesome, hopefully is sparks a good conversation.
niu tech@bramus It's a pity @jpegxl still wasn't included in Interop 2025 even though it was the most popular proposal: https://github.com/web-platform-tests/interop/issues/700
