1890815 - [css-text-3] Disambiguation about soft wrap opportunities around replaced elements

Status: NEW

(Core :: Layout: Text and Fonts, defect)

Description

[Mozilla Apprentice]

A resolution was made for csswg-drafts/#9964.

[css-text-3] Disambiguation about soft wrap opportunities around replaced elements

• RESOLVED: Clarify spec about soft-wrap oppos before/after characters to also reference atomic inlines.

Discussion.

Comment 1

[Daniel Holbert [:dholbert]]

Attachment: testcase 1 (from the spec issue)

Here's the testcase from
https://github.com/w3c/csswg-drafts/issues/9964#issue-2135216890

We produce a different rendering here from Chromium/WebKit. The csswg resolution was to follow (and encode in the spec) the Chromium/WebKit behavior.

Comment 2

[Daniel Holbert [:dholbert]]

jfkthame or TYLin: perhaps one of you know where the relevant code lives for this, in your work on linewrapping stuff? I imagine/hope this might be a relatively targeted change.

This seems to be a longstanding interop issue where we're on our own, and (as of this csswg resolution) the spec calls for the other browsers' behavior.

Comment 3

[Daniel Holbert [:dholbert]]

(Having said that, this is also pretty low priority, so no real urgency here, other than not wanting to lose track of this.)

Comment 4

[Jonathan Kew [:jfkthame]]

Agreed, it's not a top priority, though we should try to align our behavior. Offhand I'm not sure exactly where the fix needs to happen; I guess somewhere like when nsLineLayout is deciding what to do with an nsInlineFrame, but it'll need a bit of digging around. (This isn't about breaking runs of text, so the recent Segmenter and associated line-breaking changes may not be directly related.)