Re: [w3ctag/design-reviews] Rendering Independent Scroll Offsets (#409)

I think this looks pretty reasonable.  It improves consistency of these APIs with a bunch of other layout-related APIs that report unrounded positions but where the implementation pixel-snaps things later (e.g., `getBoundingClientRect`).

There is one loss of information in that prior to this change, what it sounds like Chrome and Firefox were doing reported the way the implementation did pixel-snapping -- something that I suppose could potentially be useful.

But assuming that implementations are consistent about doing pixel-snapping of scroll positions the same way they do pixel-snapping of edges (which I certainly hope is the case -- and which I'd hope would be specified in the changes proposed here), it seems like that's not a huge issue, especially since there isn't really API surface for getting the way anything *else* pixel-snaps.

In any case, @alice and I just discussed this in a breakout, and we're fine with closing this issue.

It seems worth bringing a proposal to CSS -- there may be some folks there who have additional feedback.  And I think the group should be capable of reviewing changes to cssom-view even if the spec doesn't have an active editor.

Thanks for asking the TAG for review.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/409#issuecomment-528655538