Created attachment 516992 [details]
Test case (tries to crash after 10 seconds)
If you style a first letter with a float style, and the paragraph starts at the bottom of a column, there is no room for the letter, and it "floats" to the next column. However the rest of the paragraph is then displayed in the bottom line! The browser can subsequently abort; I found that altering the column rules was most likely to trigger the abort.
###!!! ASSERTION: aForFrame not found in block, someone lied to us: 'isValid', file nsTextFrameThebes.cpp, line 1175
###!!! ABORT: comparing iterators over different lists: 'mListLink == aOther.mListLink', file nsLineBox.h, line 722
roc, this seems like your sort of thing...
Created attachment 544947 [details]
Created attachment 598348 [details]
(scroll about 60% down to see the interesting frames)
We're trying to build a text run for the text frame "N" (red) which
is the child frame of a float first-letter.
nsFirstLetterFrame::CanContinueTextRun() returns 'true' so
FindLineContainer() walks up the ancestor to 0x7fffdcf083b8 (green),
which isn't the line container for the text frame.
This should be easily fixed by returning 'false' in
CanContinueTextRun() for a floating first-letter.
Still, there's something odd about the frame tree --
why has the float been pushed into a different block from the
text is supposed to be the first letter for?
(namely 0x7fffdcd08f68 (yellow))
That seems wrong, but maybe we're not done reflowing yet?
Created attachment 598372 [details] [diff] [review]
fix + tests
Try results pending:
Hmm, it appears text-transform:capitalize assumes that the start of a text run
is also the start of a word?
Looking at the text-run / line-breaker code it looks hard to get things right
when a word is broken into two text-runs. I'll see if I can make BuildTextRuns
Created attachment 598531 [details] [diff] [review]
fix + tests
For floating first-letter text, I think the correct line-container to use
for the line iterators here is the parent of the placeholder frame.
We've just assumed that the floating first-letter parent is the same
as the placeholder parent. I think that's actually a bug when it's not,
but let's fix this crash first and then file a second bug on that.
The last two hunks fixes compile warnings - an unused variable and a
signed/unsigned int comparison.
The assert(18) are all "Computed overflow area must contain frame bounds"
due to the "margin: -562949953421311em;" in the test causing nscoord
overflows. I'm not worried about that.
The Try run:
Filed bug 729352 to follow-up on the misplaced float first-letter frame.