Closed
Bug 1151684
Opened 9 years ago
Closed 3 years ago
Assertion failure: "Unprocessed justification gaps", with "text-align: justify true;"
Categories
(Core :: Layout, defect)
Core
Layout
Tracking
()
RESOLVED
INCOMPLETE
Tracking | Status | |
---|---|---|
firefox40 | --- | affected |
People
(Reporter: jruderman, Unassigned, NeedInfo)
References
Details
(Keywords: assertion, regression, testcase)
Attachments
(3 files)
Assertion failure: applyState.mGaps.mHandled == applyState.mGaps.mCount (Unprocessed justification gaps), at layout/generic/nsLineLayout.cpp:3131 The assertion was added in https://hg.mozilla.org/mozilla-central/rev/8fd4e3a06f17 (bug 1063857). The extra text-align value was added in bug 929991. (For the state of Gecko vs state of the spec, see bug 929991 comment 26.)
Reporter | ||
Comment 1•9 years ago
|
||
To reproduce you need to set the pref: user_pref("layout.css.text-align-true-value.enabled", true);
Reporter | ||
Comment 2•9 years ago
|
||
Comment 3•9 years ago
|
||
So what should happen when text-align is "justify true"? Should "true" just be ignored? Or probably text should have negative spaces inside?
Flags: needinfo?(mats)
Updated•9 years ago
|
OS: Mac OS X → All
Hardware: x86_64 → All
Comment 4•9 years ago
|
||
I meant, if the remaining isize is negative, should we add negative spaces inside text to make it really "justify"? Or just act like normal and ignore "true"?
Comment 5•9 years ago
|
||
Comment 6•9 years ago
|
||
The spec changed after we implemented 'true' on 'text-align'. I suspect that we shouldn't implement <overflow-position> at all on text-align[-last], only on the new properties in the css-align spec, but we should ask on www-style@ to confirm this before starting to remove/change the code.
Flags: needinfo?(mats)
Comment 7•9 years ago
|
||
Well, it doesn't seem that this syntax is ever included in the spec. dbaron and roc were failed to convince the editor that this should be added to the spec. Hence the truth is that the spec didn't changed because it just had not changed for this at all. Therefore, in a forseeable future, I guess we won't enable this pref by default. Hence it's probably fine to just leave this bug as-is currenlty, and see if there will be any progress on make it speced.
Comment 8•3 years ago
|
||
Hey Jesse,
Can you still reproduce this issue or should we close it?
Flags: needinfo?(jruderman)
Comment 9•3 years ago
|
||
Marking this as Resolved > Incomplete as per reporter's lack of response.
If anyone can still reproduce this issue re-open it or file a new bug.
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•