Assertion failure: applyState.mWidth.mConsumed == applyState.mWidth.mAvailable (Unprocessed justification width), at /builds/worker/workspace/build/src/layout/generic/nsLineLayout.cpp:3187 with XUL -moz-grid-line and vertical writing mode
Categories
(Core :: XUL, defect, P5)
Tracking
()
People
(Reporter: jkratzer, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: assertion, testcase, Whiteboard: [fuzzblocker])
Attachments
(1 file)
225 bytes,
text/html
|
Details |
Updated•6 years ago
|
Comment 1•6 years ago
|
||
Updated•6 years ago
|
Comment 2•4 years ago
|
||
The fuzzers are tripping over this frequently. Marking as fuzzblocker.
Mats: Are you able to take this issue?
Comment 3•4 years ago
|
||
Nope, I refuse to make any kind of "improvements" to XUL layout. XUL layout code should be removed, that's the only thing I'll contribute to when it comes to XUL.
We should stop using display:-moz-grid
in our UI so that we can finally remove it.
It looks like it's close, there's only one remaining usage that I can find:
toolkit/components/prompts/content/tabprompts.jsm
Maybe Gijs can say how hard it would be to convert that one to use display:grid/flex
instead?
Comment 4•4 years ago
|
||
bug 1583696 covers removing xul grid from tabprompts. It's not really trivial because there's no 1-1 corresponding CSS/markup that can be used instead, and the previous attempt in that bug got backed out over a number of regressions in the prompt display - tab prompts have to cope with almost arbitrary input from websites, as well as arbitrary window sizes, so getting them to behave correctly in all cases is not trivial.
At this point, tbh, I'd sooner switch tab prompts over to the new-style in-content prompts -- but that'd probably want some discussion around styling, to avoid the impression that the contents come from the browser, and so on. It may end up being part of the proton work in the next 2-3 months; it may not.
Updated•4 years ago
|
Updated•4 years ago
|
Description
•