[css-scroll-snap-2] Should SnapEvents report multiple aligned targets?

[DavMila]

The snap events spec defines the SnapEvent interface as representing only one snapped-to element in each axis. However, it is possible for multiple elements to be visually snapped to, even if a user-agent internally selects only one target. E.g. in this codepen snapping to align to any box also makes the scroller snap-aligned to the other boxes in the row.

It would be good to get a resolution on whether SnapEvents should report all the visually-aligned targets or just the one the user-agent has internally picked.

When a layout change occurs such that previously aligned snap areas are no longer aligned, the scroller will follow the snap area that was selected as the snap target, so it might be better to have SnapEvents expose this single target so that a developer can tell which snap area would be followed through a layout change and style/animate/highlight their snap areas accordingly.

[flackr]

I believe we already agreed in #9622 that we should expose the single element, it was the first part of the issue.

[DavMila]

Thanks for the pointer. Closing this as Won't fix.