We've shipped a mitigation for this issue in bug 1681052. It won't handle all cases perfectly -- e.g. it might cut a line of text in half -- but there shouldn't be as much missing content due to this bug anymore. The spec text from comment 11 still exists and has been extended a bit: > Since line boxes contain no possible break points, inline-block and inline-table boxes (and other inline-level display types that establish an independent formatting context) may also be considered monolithic: that is, in the cases where a single line box is too large to fit within its fragmentainer even by itself and the UA chooses to split the line box, it may fragment such boxes or it may treat them as monolithic. https://drafts.csswg.org/css-break/#end-block Also, a bit further along, the spec says: > [...] the UA may also fragment the contents of monolithic elements by slicing the element’s graphical representation. https://drafts.csswg.org/css-break/#unforced-breaks So: given the following... - Our new behavior as of bug 1681052 is matching these two bits of spec text (treating inline-* content as monolithic and slicing its graphical representation) - We believe our approach mitigates the dataloss that we were reporting here - The three testcases all pass (all of the content is visible in print preview) ...I think we can close this as FIXED-by-bug 1681052. If there are any remaining issues associated with this bug, we should spin them off to their own bug reports and give them individual consideration/treatment.
Bug 534182 Comment 22 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
We've shipped a mitigation for this issue in bug 1681052. It won't handle all cases perfectly -- e.g. it might cut a line of text in half -- but there shouldn't be as much missing content due to this bug anymore. The spec text from comment 11 still exists and has been extended a bit: > Since line boxes contain no possible break points, inline-block and inline-table boxes (and other inline-level display types that establish an independent formatting context) may also be considered monolithic: that is, in the cases where a single line box is too large to fit within its fragmentainer even by itself and the UA chooses to split the line box, it may fragment such boxes or it may treat them as monolithic. https://drafts.csswg.org/css-break/#end-block Also, a bit further along, the spec says: > [...] the UA may also fragment the contents of monolithic elements by slicing the element’s graphical representation. https://drafts.csswg.org/css-break/#unforced-breaks So: given the following... - Our new behavior as of bug 1681052 is matching these two bits of spec text (treating inline-* content as monolithic and slicing its graphical representation) - We believe our approach mitigates the dataloss that we were reporting here - The three testcases all pass (all of the content is visible in print preview) ...I think we can close this as FIXED-by-bug 1681052. If there are any remaining issues associated with this bug, we should spin them off to their own bug reports and give them individual consideration/treatment.