Open
Bug 1384681
Opened 8 years ago
Updated 2 years ago
stylo: Need to figure out what to do with the hacky style re-resolution that nsSplitterFrame does.
Categories
(Core :: CSS Parsing and Computation, enhancement, P4)
Core
CSS Parsing and Computation
Tracking
()
NEW
People
(Reporter: emilio, Unassigned)
References
Details
There's a little nasty piece of code in[1] that right now will make us crash:
Even grabbing the correct style context parent there, we would still need to actually re-resolve the style, instead of just grabbing it from the element.
That piece of code is nasty enough I don't really want to write a specific API just for it, and it probably doesn't block releasing 57 if we don't style xul stuff with Stylo, but sill need to think about it.
[1]: http://searchfox.org/mozilla-central/rev/8a61c71153a79cda2e1ae7d477564347c607cc5f/layout/xul/nsSplitterFrame.cpp#283
Updated•7 years ago
|
Priority: -- → P4
Updated•7 years ago
|
status-firefox57:
--- → wontfix
status-firefox58:
--- → fix-optional
Comment 1•7 years ago
|
||
status-firefox59:
--- → ?
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•