1630258 - A sticky table element in a grid layout is sometime rendered in wrong places after scrolling with keyboard.

Status: RESOLVED DUPLICATE of bug 1472602

(Core :: Layout: Grid, defect, P3)

Description

[Frank Nagel]

Attachment: grid_sticky_align_start.html

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:75.0) Gecko/20100101 Firefox/75.0

Steps to reproduce:

Open the attached HTML file with Firefox and use the Page-Down and Page-Up keys to scroll to the bottom and back up. Alternatively use the mouse to drag the scrollbar down and up.

Using the mouse wheel does not trigger the bug.

Actual results:

In the rightmost column the sticky element gets stuck in arbitrary vertical positions.

Expected results:

Like the other two sticky elements to the left, the rightmost sticky element should return to the top after scrolling back up.

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

Bugbug thinks this bug should belong to this component, but please revert this change in case of error.

Comment 2

[Firefox Bug Husbandry Bot]

Resetting severity to default of --.

Comment 3

[Jonathan Kew [:jfkthame]]

Yes, this looks pretty broken -- it reproduces for me on macOS using the trackpad to scroll, fwiw.

Tentatively moving to Layout:Grid, as that seems to be a key part of the testcase; Mats, can you take a look?

Comment 4

[Firefox Bug Husbandry Bot]

Because this bug's Severity has not been changed from the default since it was filed, and it's Priority is P3 (Backlog,) indicating it has been triaged, the bug's Severity is being updated to S3 (normal.)

Comment 5

[BugBot [:suhaib / :marco/ :calixte]]

Clear a needinfo that is pending on an inactive user.

Inactive users most likely will not respond; if the missing information is essential and cannot be collected another way, the bug maybe should be closed as INCOMPLETE.

For more information, please visit BugBot documentation.

Comment 6

[Ting-Yu Lin [:TYLin] (PDT, UTC-7)]

mozregression finds this range https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=db8bb8422d1fdfb2cd32d6ec3a60ec0743f93aed&tochange=3d57939c67790a99d1f485f8d7f56c4b3047ed75

It's likely fixed by bug 1472602.