Closed
Bug 1146117
Opened 9 years ago
Closed 9 years ago
"ASSERTION: No ruby base ancestor?" with <select>
Categories
(Core :: Layout, defect)
Core
Layout
Tracking
()
RESOLVED
FIXED
mozilla40
| Tracking | Status | |
|---|---|---|
| firefox40 | --- | fixed |
People
(Reporter: jruderman, Assigned: xidorn)
References
Details
(Keywords: assertion, testcase)
Attachments
(3 files)
###!!! ASSERTION: No ruby base ancestor?: 'aFrame', file layout/generic/nsLineLayout.cpp, line 2906
|
Reporter | |
Comment 1•9 years ago
|
||
|
Assignee | |
Comment 2•9 years ago
|
||
This is a known assertion. It is too tricky to completely fix problems like this, as discussed in bug 1138092.
Status: NEW → RESOLVED
Closed: 9 years ago
OS: Mac OS X → All
Hardware: x86_64 → All
Resolution: --- → WONTFIX
An assertion failure is saying that an assumption of the code is being violated. If that's not the case, then we shouldn't have an assertion; if it is, we need to fix it. We shouldn't WONTFIX assertion failures that result from unprivileged Web content.
Status: RESOLVED → REOPENED
Resolution: WONTFIX → ---
|
|
Reporter | |
Comment 4•9 years ago
|
||
You could downgrade the assertion to a warning if you want to keep seeing it. Eventually, unexpected warnings will be considered regression test failures (bug 1080457) -- in contrast to assertions, which are bugs whether "expected" or not.
|
|
Assignee | |
Comment 5•9 years ago
|
||
OK, so downgrade this assertion. Probably we will eventually remove this warning, if ShouldSuppressLineBreak bit is also used by some other feature in the future.
Assignee: nobody → quanxunzhen
Attachment #8590023 -
Flags: review?(dbaron)
Attachment #8590023 -
Flags: review?(dbaron) → review+
|
|
Assignee | |
Comment 6•9 years ago
|
||
https://hg.mozilla.org/integration/mozilla-inbound/rev/c4d86ce81aab
https://hg.mozilla.org/mozilla-central/rev/c4d86ce81aab
Status: REOPENED → RESOLVED
Closed: 9 years ago → 9 years ago
status-firefox40:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla40
You need to log in
before you can comment on or make changes to this bug.
Description
•