Closed
Bug 1495962
Opened 6 years ago
Closed 5 years ago
Floating table header moves and snaps back when scrolling down (should'nt move at all)
Categories
(Core :: Graphics: WebRender, defect, P2)
Tracking
()
People
(Reporter: mayankleoboy1, Assigned: kats)
References
(Blocks 1 open bug, )
Details
(Keywords: nightly-community, regression)
Attachments
(3 files)
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:64.0) Gecko/20100101 Firefox/64.0 Steps to reproduce: 1. Enable WR 2. Go to https://www.androidcentral.com/poco-f1-vs-oneplus-6 3. There is a comparison table in the middle of the page 4. Scroll down from the table Actual results: the "floating" table header moves down, and then snaps back continously From the looks of it, this is a APZC+WR bug Expected results: not so.
Reporter | ||
Comment 2•6 years ago
|
||
I am scrolling using the mousepad on a laptop
Comment 3•6 years ago
|
||
A regression date would have to be before 2018-01-15.
Blocks: webrender-site-issues, stage-wr-trains
status-firefox62:
--- → disabled
status-firefox63:
--- → disabled
status-firefox64:
--- → affected
Flags: needinfo?(jan)
OS: Unspecified → All
Priority: -- → P3
Comment 4•6 years ago
|
||
It's broken since it was implemented:
> Emilio Cobos Álvarez — Bug 975644: Enable position sticky in table parts. r=bz
status-firefox-esr60:
--- → disabled
status-geckoview62:
--- → disabled
Flags: needinfo?(jan)
Keywords: regressionwindow-wanted
Reporter | ||
Comment 5•6 years ago
|
||
well, this reproduces only with WR for me.
Assignee | ||
Comment 6•6 years ago
|
||
Thanks. I can look at this when I'm done my current set of bugs. Leaving unassigned for now in case somebody else wants to do it first.
Flags: needinfo?(kats)
Comment 7•6 years ago
|
||
Marking fix-optional for 64. We could still take a patch for 65, and if it's verified and doesn't seem risky, could still take fixes for 64 as well.
Updated•6 years ago
|
Priority: P3 → P2
Updated•5 years ago
|
Assignee: nobody → kats
Assignee | ||
Comment 8•5 years ago
|
||
Minimal testcase to repro. Basically, both the <tr> and the <th> are sticky-positioned, so presumably we end up applying the sticky offset twice, or something like that. With async scrolling the header ends up moving against the scroll instead of staying in place.
Assignee | ||
Comment 9•5 years ago
|
||
https://treeherder.mozilla.org/#/jobs?repo=try&group_state=expanded&revision=9248c1317a942a91216c4cfde0bc58f71a71f85b
Assignee | ||
Comment 10•5 years ago
|
||
Assignee | ||
Updated•5 years ago
|
See Also: → https://github.com/servo/webrender/pull/3427
Assignee | ||
Comment 11•5 years ago
|
||
https://treeherder.mozilla.org/#/jobs?repo=try&group_state=expanded&revision=f40f9ac5dfe05ebb6793b3d81ac4fcae3d68d49e
Comment 12•5 years ago
|
||
Pushed by kgupta@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/90db69624281 Add reftests for nested sticky-positioning r=kvark
Comment 13•5 years ago
|
||
Backed out changeset 90db69624281 (Bug 1495962) for reftest failures in reftests/position-sticky/nested-sticky-2.html DONTBUILD Failure log: https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=217619196&repo=autoland&lineNumber=2201 https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=217619215&repo=autoland&lineNumber=15068 Push with failures: https://treeherder.mozilla.org/#/jobs?repo=autoland&resultStatus=testfailed%2Cbusted%2Cexception%2Cusercancel%2Crunnable&revision=1fbdcb9480daf162357da72ee263c41165bcac27&selectedJob=217623217&searchStr=windows%2C7%2Creftest Backout: https://treeherder.mozilla.org/#/jobs?repo=autoland&resultStatus=testfailed%2Cbusted%2Cexception%2Cusercancel%2Crunnable&revision=7b860a9f49a97c6c67b6f4cae452c1630ac17079
Flags: needinfo?(kats)
Comment 15•5 years ago
|
||
Pushed by kgupta@mozilla.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/e023011bce62 Add reftests for nested sticky-positioning r=kvark
Comment 16•5 years ago
|
||
Pushed by kgupta@mozilla.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/276e3568f74f Follow-up to fix overeager fuzzing. r=me
Comment 17•5 years ago
|
||
Pushed by kgupta@mozilla.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/05d1120d5b91 Loosen fuzz range for win 7 reftest jobs. r=me
Comment 18•5 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/e023011bce62 https://hg.mozilla.org/mozilla-central/rev/276e3568f74f https://hg.mozilla.org/mozilla-central/rev/05d1120d5b91
Status: NEW → RESOLVED
Closed: 5 years ago
status-firefox66:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla66
Updated•5 years ago
|
status-firefox65:
--- → ?
Assignee | ||
Comment 19•5 years ago
|
||
WR only, not severe/common enough to uplift, I would say.
Updated•5 years ago
|
Status: RESOLVED → VERIFIED
Comment 20•5 years ago
|
||
Hello,
Confirming this issue as verified fixed on Windows 10x64 with 66.0b14 and 67.0a1 (2019-03-08)on an nVidia GTX 1060 GPU.
status-firefox67:
--- → verified
You need to log in
before you can comment on or make changes to this bug.
Description
•