Some ProcessRestyledFrames cleanups.
Categories
(Core :: CSS Parsing and Computation, enhancement)
Tracking
()
Tracking | Status | |
---|---|---|
firefox95 | --- | fixed |
People
(Reporter: emilio, Assigned: emilio)
References
Details
Attachments
(4 files)
Bug 1736558 - Factor out containing block change processing to its own function. r=#layout-reviewers
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review |
Assignee | ||
Comment 1•3 years ago
|
||
No behavior change.
Assignee | ||
Comment 2•3 years ago
|
||
Depends on D128872
Assignee | ||
Comment 3•3 years ago
|
||
Depends on D128873
Assignee | ||
Comment 4•3 years ago
|
||
Shouldn't have any behavior change either and is more similar to the
containing block reframe.
Depends on D128874
Updated•3 years ago
|
Comment 6•3 years ago
|
||
Minor followup - per my afterthought in the last patch (RE the discussion about null-checks there), I think we can also promote the explicit null-check to an assertion in TryToHandleContainingBlockChange
as well (the function added in the first patch here), right?
Here in particular:
https://hg.mozilla.org/integration/autoland/annotate/1943f99e1345bd243f3ee6c68d37bfcae4b95ac1/layout/base/RestyleManager.cpp#l1356
If I'm understanding that correctly, would you mind landing that as a followup? That'll make us more consistent about how we depend on & validate that invariant in that section of code.
Comment 7•3 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/753d2e8989de
https://hg.mozilla.org/mozilla-central/rev/ea8736bd655c
https://hg.mozilla.org/mozilla-central/rev/29c466b6238f
https://hg.mozilla.org/mozilla-central/rev/1943f99e1345
Assignee | ||
Comment 8•3 years ago
|
||
Comment 9•3 years ago
|
||
bugherder |
Description
•