On Wed, Jun 5, 2024 at 12:16 PM Philip Jägenstedt <foo...@chromium.org> wrote:
> Developer excitement about this is evident in > https://github.com/w3c/csswg-drafts/issues/156. It was filed by a web > developer and the 100 thumbs up are probably mostly from other web > developers. > > These events seem like obvious missing functionality similar to the > scrollend events, without the events you need to listed to scroll events > and guess when it has come to a stop. > > That being said, examples of what can be built with these events would be > very nice. For the scrollsnapchange event it's easy to imagine updating > some state below a carousel to match the snapped element, such as item > description or store inventory. For scrollsnapchanging I don't dare hazard > a guess, can someone say what the canonical use case for this is? > IMO scrollsnapchanging is the more useful event. It has a similar purpose to what the input event is prior to the change event fired on form controls or the scroll event is to scrollend, being an earlier signal of the eventual final result which can be useful for immediate feedback. scrollsnapchanged could be inferred by the combination of the latest scrollsnapchanging before the scrollend event. For carousels, it can be extremely useful for immediate feedback when the carousel is scrolling to a particular item to highlight the destination right away. E.g. right now the carousels on https://gui-challenges.web.app/carousel/dist/ only update on scrollend but in many native carousels (e.g. https://www.airbnb.ca/) the active item is updated throughout the scroll before it settles. Looping in @Adam Argyle <arg...@google.com> > > On Thu, May 30, 2024 at 1:57 AM Alex Russell <slightly...@chromium.org> > wrote: > >> Ok, looking at these explainers, I'm not sure we have enough to go on to >> approve this Intent right now. >> >> First, use-cases are listed, but no example code is provided to show what >> developers have to do today vs. how this new design will address what's >> problematic about the current situation. These documents are regurgitated >> IDL with no considered alternatives provided. It also isn't clear if or why >> the SnapEvent interface contains enough information to address any of the >> listed use-cases. >> >> As we'd be going first, I'd be looking for some amount of developer >> support to move forward. Is there a reason this isn't going to OT to get >> that sort of input? >> >> Best, >> >> Alex >> >> >> >> On Wednesday, May 29, 2024 at 4:48:36 PM UTC-7 Alex Russell wrote: >> >>> For the avoidance of doubt, we don't block on WG consensus. If there's >>> sufficient evidence that a feature has been developed with high quality and >>> strong developer support, that's enough for us. CSS WG blessing is strictly >>> nice-to-have. >>> >>> On Tuesday, May 28, 2024 at 4:37:39 PM UTC-7 Emilio Cobos Alvarez wrote: >>> >>>> Sounds good, thanks Tab! >>>> >>>> -- Emilio >>>> >>>> On Tue, May 28, 2024, 22:47 Tab Atkins Jr. <jackalm...@gmail.com> >>>> wrote: >>>> >>>>> On Mon, May 27, 2024 at 1:04 PM 'Emilio Cobos Álvarez' via blink-dev >>>>> <blink-dev@chromium.org> wrote: >>>>> > Has this been reviewed by the CSSWG? (not only the PR I mean, but the >>>>> > feature as a whole). The spec PR: >>>>> > https://github.com/w3c/csswg-drafts/pull/9515 >>>>> > >>>>> > Doesn't mention any issue or discussion in a CSSWG call. Usually >>>>> having >>>>> > a resolution for a new feature is a requirement to get it merged... >>>>> > >>>>> > We recently discussed a similar process mishap in >>>>> > https://github.com/w3c/csswg-drafts/issues/7767, would be good not >>>>> to >>>>> > repeat it. >>>>> >>>>> The feature was discussed and resolved on back in 6985 >>>>> < >>>>> https://github.com/w3c/csswg-drafts/issues/6985#issuecomment-1049029573 >>>>> > >>>>> (the issue is originally just about pseudo-classes, but the discussion >>>>> on the call was about snap events as well, and the resolution covered >>>>> that explicitly). We've also discussed some of the features's issues >>>>> in the WG in the last few months. >>>>> >>>>> But since it's been a while since the original resolution, I've gone >>>>> ahead and tagged 6985 with Agenda+ just to give a heads-up to the >>>>> group. (David and flackr will be able to discuss it on the WG call >>>>> next week; I'll be at CSS Day. Or we can talk about it at the f2f in >>>>> two weeks.) >>>>> >>>>> > I see some follow-up issues on naming and such things are still open >>>>> > (though some /do/ have resolutions). Do you plan to update the spec >>>>> and >>>>> > tests? >>>>> >>>>> The relevant issues have all been resolved, but you're right, only the >>>>> naming one had been editted so far. David's working on the other two >>>>> (bubbling, and pseudo-elements), and we'll get them reviewed and >>>>> merged asap. Thanks for the heads up. >>>>> >>>>> ~TJ >>>>> >>>> -- >> 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/50e066e9-c852-403d-970c-6a1e691cdb98n%40chromium.org >> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/50e066e9-c852-403d-970c-6a1e691cdb98n%40chromium.org?utm_medium=email&utm_source=footer> >> . >> > -- > 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/CAARdPYfmkDtPv6vW_dbhB6WAayVkkLor0fsRdtdK5rcVU_1%2BYw%40mail.gmail.com > <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAARdPYfmkDtPv6vW_dbhB6WAayVkkLor0fsRdtdK5rcVU_1%2BYw%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > -- 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/CAJh39TPv9QShncF3tXK00NjJYi%3DY_9QF%2BsLYa1GfR3Ttc_s0ig%40mail.gmail.com.
