Open Bug 1553770 Opened 5 years ago Updated 2 years ago

Consider using the given range in ScrollByCSSPixels (or such) for scroll snapping

Categories

(Core :: Layout: Scrolling and Overflow, enhancement, P3)

Product:
Core
Component:
Layout: Scrolling and Overflow
Type:
enhancement

Tracking

()

People

(Reporter: hiro, Unassigned)

References

(Blocks 1 open bug)

Details

From a review comment by botond

I'm not very familiar with the history of this code and the purpose of the aRange parameter (it seems to be related to sub-pixel alignment?), but I wonder if we should be making more of an effort to preserve the range in the case we're scroll snapping. For example, if the range was a half pixel in each direction, we could just re-center it around the new destination, rather than than replacing it with an empty range.

Perhaps we can file a follow-up bug about this, and ask Timothy and/or Mats (and/or Markus though he's on vacation) for an opinion?

From what I can tell is that such situation rarely happens since normally snapping changes the final destination position far from the given range. That's said, there seems be some edge cases where such sub-pixel alignment happens (presumably with a big device-pixel ratio) so it's probably worth considering.

Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.