Open Bug 1518636 Opened 5 years ago Updated 2 years ago

Precisely calculate anchor suppression triggers for absolute position changes

Categories

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

enhancement

Tracking

()

People

(Reporter: rhunt, Assigned: rhunt)

References

(Blocks 1 open bug)

Details

The scroll anchoring specification lists changes to 'position: absolute' as triggering a scroll adjustment suppression [1].

Currently Gecko handles changes to 'position: absolute' by reframing. The current scroll anchoring implementation handles this by detecting when the topmost frame to be reframed changes being absolutely positioned.

This is not correct, as it's possible that an absolute position change could be swallowed by an ancestor frame being reframed.

It's not clear whether this will be an issue, as suppression triggers are heuristics to mitigate some potential feedback loops that could happen, and this solution might be good enough. It currently passes the WPT suite.

[1] https://drafts.csswg.org/css-scroll-anchoring-1/#suppression-triggers

Priority: -- → P3

This shouldn't block release of scroll anchoring.

No longer blocks: scroll-anchoring-release
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.