nsBidiPresUtils line iterator can get off due to mPrevFrame being out of sync due to ResolveParagraphWithinBlock
Categories
(Core :: Layout: Block and Inline, defect)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox70 | --- | fixed |
People
(Reporter: dbaron, Assigned: dbaron)
References
Details
Attachments
(4 files)
I need nsBidiPresUtils's line iterator to be accurate to fix bug 1300293, and an assertion I wrote caught that it was not accurate while loading https://html.spec.whatwg.org/ . (No need to view source, like in that bug!)
The patch will explain what the problem was.
(It's... not the only such problem and I haven't gotten the patch working yet, but it does fix the assertion included in this patch.)
| Assignee | ||
Comment 1•6 years ago
|
||
| Assignee | ||
Comment 2•6 years ago
|
||
| Assignee | ||
Comment 3•6 years ago
|
||
| Assignee | ||
Comment 4•6 years ago
|
||
| Assignee | ||
Comment 5•6 years ago
|
||
That said, it's possible I should instead change this in BidiParagraphData::ResetData, whose only caller is nsBidiPresUtils::ResolveParagraphWithinBlock. But then it would happen even if resolving the inner paragraph doesn't create new continuations. I'm not sure what you think about that tradeoff.
Also, here's a try run.
| Assignee | ||
Updated•6 years ago
|
| Assignee | ||
Comment 6•6 years ago
|
||
Interestingly, there was a bug I missed in the first version (the addition of the second null assignment that I've now added related to SplitInlineAncestors) that showed up by my assertion firing while doing view-source of the HTML spec... but didn't show up anywhere in our testsuite. So it seems like I should probably figure out how to add a test for that...
| Assignee | ||
Comment 7•6 years ago
|
||
Here's a new try run.
Comment 9•6 years ago
|
||
| bugherder | ||
Description
•