Visual glitch when hiding table columns, with retained display lists
Categories
(Core :: Web Painting, defect, P3)
Tracking
()
People
(Reporter: ed, Unassigned)
References
(Regression)
Details
(Keywords: regression, Whiteboard: [triagemonth-2019-06])
Attachments
(3 files)
When hiding all the cells in a table column (using JavaScript and display: none), it seems that Firefox does not redraw the table completely.
I've attached a test case. When I click "Hide column 2", the bug occurs: the column is hidden but the background of each remaining table cell is not repainted.
I've tried this in version 67.0.4 and a nightly build, with the same result.
Note that if I somehow force a repaint (e.g., by resizing the browser window), then the table gets redrawn correctly.
Updated•6 years ago
|
Comment 3•6 years ago
|
||
Hi Ed!
Thanks for taking your time to report this issue. I can reproduce this issue on my Windows 10 (64 bit) machine.
After clicking the Hide column 2 button the column is hidden but the background of each remaining table cell is not repainted and it moves to its position as soon as I go to a different tab!
As, I can reproduce the issue, I am confirming this bug.
Comment 4•6 years ago
|
||
The priority flag is not set for this bug.
:dholbert, could you have a look please?
For more information, please visit auto_nag documentation.
Comment 5•6 years ago
|
||
I can reproduce as well. This is a regression, too. Regression range:
1:11.64 INFO: Last good revision: b79457b703d9b51cf3e38199f4e154d21bc6fc97 (2018-07-13)
1:11.64 INFO: First bad revision: 04dd259d71db60341016eccf53ced43742319631 (2018-07-14)
1:11.64 INFO: Pushlog:
https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=b79457b703d9b51cf3e38199f4e154d21bc6fc97&tochange=04dd259d71db60341016eccf53ced43742319631
Comment 6•6 years ago
|
||
In that regression range, I'm tentatively assuming bug 1475413 is the culprit.
Comment 7•6 years ago
|
||
Yeah, I get "expected results" if I toggle about:config pref layout.display-list.retain = false
, which basically confirms that bug 1475413 would've been the cause of this bug.
Updated•3 years ago
|
Updated•2 years ago
|
Description
•