RE: [css-snappoints][css-scroll-snap] Fragment ID and scroll-snapping

> But it occurs to me that we could easily do the opposite: if an element is linked to via its fragment ID, snap to its snap position if it defines one.

I like the functionality, but I'm not sure how consistent it would be.

Fragment navigation is pretty loosely defined (e.g. "Spin the event loop for a user-agent-defined amount of time, as desired by the user agent implementor.") [1].  I think there would be a race condition between normal fragment navigation and the application of the snap-point style, right?  If so, it seems the outcome would alter the user experience.

Thanks,
-Matt

[1] http://www.w3.org/TR/html5/browsers.html#navigate 

Received on Tuesday, 20 October 2015 16:59:23 UTC