Columns can be resized to overlap.
Categories
(DevTools :: Storage Inspector, defect, P2)
Tracking
(firefox-esr102 unaffected, firefox106 unaffected, firefox107 wontfix, firefox108 verified)
Tracking | Status | |
---|---|---|
firefox-esr102 | --- | unaffected |
firefox106 | --- | unaffected |
firefox107 | --- | wontfix |
firefox108 | --- | verified |
People
(Reporter: 6k64x4ma, Assigned: emilio)
References
(Regression)
Details
(Keywords: regression)
Attachments
(2 files)
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:107.0) Gecko/20100101 Firefox/107.0
Steps to reproduce:
- Open the Storage Inspector.
- Resize columns in the table widget.
Actual results:
Columns can be resized to overlap.
Expected results:
It shouldn't be possible.
![]() |
||
Updated•7 months ago
|
![]() |
||
Updated•7 months ago
|
Comment 1•7 months ago
|
||
:emilio, since you are the author of the regressor, bug 1792473, could you take a look? Also, could you set the severity field?
For more information, please visit auto_nag documentation.
Assignee | ||
Comment 2•7 months ago
|
||
It was needed only for sticky to work on XUL and it's not needed anymore.
The way splitters work on modern flexbox is that they take the min-width
property of the element they're resizing (without looking at descendants).
This is done for performance reasons (flex item min-width is more expensive to
compute on isolation than XUL flex was). Removing the wrapper makes the
min-width be on the right element anyways.
Updated•7 months ago
|
Assignee | ||
Updated•7 months ago
|
Updated•7 months ago
|
Pushed by ealvarez@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/c78b0be860b1 Remove table-widget-wrapper. r=jdescottes
Pushed by ctuns@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/1772e0cda827 Fix lint failure r=fix CLOSED TREE
Comment 5•7 months ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/c78b0be860b1
https://hg.mozilla.org/mozilla-central/rev/1772e0cda827
Updated•7 months ago
|
Updated•6 months ago
|
Updated•6 months ago
|
Comment 6•6 months ago
|
||
Reproduced the issue on Nightly 108.0a1 build from 2022-10-29.
Verified it on Beta 108.0b5 build on MacOS 12 ARM, Windows 10 and Ubuntu 22.04, and can confirm that the issue is fixed.
Description
•