Consider enabling the optimization to not flush when getting fixed margins from getComputedStyle().
Categories
(Core :: Layout, defect, P3)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox70 | --- | fixed |
People
(Reporter: emilio, Assigned: emilio)
References
Details
Attachments
(2 files)
This would align (dubiously) our behavior with other engines, but it's not 100% clear whether that's right, see https://github.com/w3c/csswg-drafts/issues/2328.
See the following test-case for a bit of surprising behavior. If you have fixed margins, we return the "wrong" used margin, but as soon as you have a percentage margin, presumably we store the UsedMarginProperty on the frame, and return the "proper" margin.
Our behavior is inconsistent, so it's unclear what to do here...
Comment 1•6 years ago
|
||
The priority flag is not set for this bug.
:jwatt, could you have a look please?
For more information, please visit auto_nag documentation.
Updated•6 years ago
|
Updated•6 years ago
|
| Assignee | ||
Comment 2•6 years ago
|
||
Yeah, I guess we should do this.
| Assignee | ||
Comment 3•6 years ago
|
||
As noted this changes behavior, but it's unclear per
https://github.com/w3c/csswg-drafts/issues/2328 what behavior is correct, and
our behavior is inconsistent depending on whether there's any percentage
involved.
This matches other browsers so it's pretty low risk I'd say.
The test starts passing without changes to the test, but given the CSSWG issue I
made the test not rely on the optimization.
Comment 9•6 years ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/7fa833ff0b1c
https://hg.mozilla.org/mozilla-central/rev/c1311fe97e4d
https://hg.mozilla.org/mozilla-central/rev/ce4121497815
Comment 11•6 years ago
|
||
| bugherder uplift | ||
Description
•