David Bokan
David Bokan
Traditional fragment navigation is [defined by HTML](https://html.spec.whatwg.org/multipage/browsing-the-web.html#scroll-to-fragid). Scroll to text is an extension of this behavior; as such, much of the draft spec is monkey patching HTML (with a few...
Right, the offset for element E can be calculated as: `offset.y = E.getBoundingClientRect().y - document.documentElement.getBoundingClientRect().y` But it has a (maybe a bit of esoteric) edge-case. If the page adds an...
I can do it but I won't have the time to do it in the next few weeks
> with the default null value it's roughly like using a DOM API, with type of wheel you get whatever events scrolling with a mouse wheel would produce (if that's...
Friendly ping as Chromium is getting ready to send out an intent to ship for this and we'd like to get a signal from WebKit before we do so.
FYI: we've sent out an [intent-to-ship](https://groups.google.com/u/2/a/chromium.org/g/blink-dev/c/S67zJ1AYW2U) for this on blink-dev targeting M123.
For completeness: this proposal relies on the `pagereveal` event - [Webkit Position Issue](https://github.com/WebKit/standards-positions/issues/303)
FYI: Renamed this to "Cross-Document View Transitions" since L2 version of the spec contains a couple of different concepts in addition to cross-document transitions.
Hmm, I'm not an editor so not sure if that's ok - perhaps @smfr or @emilio could take a look?