Thanks for the link, Phillip. Absolutely agree that this is an unmet need and something we should have added long ago; I'd just like to see evidence that we're matching that need with a sufficient solution and that we've done our homework. There's almost nothing worse than getting to the end of a launch and realizing that some important use-cases isn't covered, and I don't have confidence based on what we've produced that we would not end up in this situation.
An exhaustive explainer with considered alternatives and sample code would unblock this from my end. Best, Alex On Wednesday, June 5, 2024 at 9:48:48 AM UTC-7 David Awogbemila wrote: > >>>>> Hi Alex, thanks for yout input! >>>>> >>>>> (Like Tab said, we’re planning to have a review of the feature as a >>>>> whole so I plan to share any feedback from that here, but since that >>>>> won’t >>>>> happen for at least another week, I wanted to update this thread in the >>>>> meantime.) >>>>> >>>>> I'm now hosting the explainer >>>>> <https://github.com/DavMila/ScrollSnapExplainers/tree/update/js-snapChanged> >>>>> >>>>> and I've updated it to reflect the research and investigation which went >>>>> into the API design (which I certainly should have done earlier). We've >>>>> discussed all of the non-trivial decisions made for the API over many >>>>> CSSWG >>>>> issues >>>>> <https://github.com/w3c/csswg-drafts/issues?q=is%3Aissue+label%3Acss-scroll-snap-2+>. >>>>> >>>>> The API choices reflect the minimum amount of information that meets the >>>>> needs of use cases we have evidence >>>>> <https://github.com/DavMila/ScrollSnapExplainers/tree/update/js-snapChanged#interest-in-snap-events> >>>>> >>>>> of interest in: the element that was selected as the snap target, and >>>>> deferred adding other bits of information for which we don't have quite >>>>> as >>>>> much evidence. We think that an origin trial might bring to light other >>>>> things that could be added to the interface but is not likely to provide >>>>> more information about the single data point we've currently put in the >>>>> interface (the selected element, which satisfies most of the use cases we >>>>> are aware of) so we thought not blocking that piece on an origin trial >>>>> might be a good idea. Happy to hear further thoughts. >>>>> >>>> -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscr...@chromium.org. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/2d8e3953-c6f7-4b88-abf4-e4ed4b128e49n%40chromium.org.
