Bug 140388 – Range is incorrectly normalized after adding into selection for u HTML element.

• Component: DOM
• Status: RESOLVED CONFIGURATION CHANGED

Created attachment 244507 [details]
Reproduction example

Creating range for text node in u HTML element and adding it to selection cause incorrectly range normalization to it's parent. See attached example for more details. Please note, that this bug occur not only for u element but for inline elements in general i.e. i, em, b. This bug does not occur for block elements like p or div.

This behaviour impact http://dev.ckeditor.com/ticket/12690 in CKEditor.

Reproduced on latest nightly r178314

[Piotrek Koszuliński (Reinmar)]

Rephrasing the bug report: Selection anchored in a text node inside an inline element (e.g. <u>) is incorrectly normalised by Webkit - it is moved to a text node outside that <u> element.

While Webkit normalising an element-anchored selection to a closest text node is a fact (a sad one :)), I would expect that it does not affect selections anchored in text nodes. This looks like some pretty new regression, because I've never seen Webkit doing this.

Of course, none other browser behave this way, but that's due to the fact that none other browser normalise selection.

[Alexey Proskuryakov]

Can you figure out when this started? That would significantly increase the chances of this being fixed.

[Ahmad Saleem]

I am able to reproduce this bug in Safari 15.6 on macOS 12.5 using attached test case and it returns "f" in the console while in other browsers (Chrome Canary 106 and Firefox Nightly 105), it returns "o" in the console. Thanks!

[Radar WebKit Bug Importer]

<rdar://problem/98460579>

[Ahmad Saleem]

Safari 16.4 shows 'f' (not expected) but Safari Technology Preview 166 show 'o' in Console. Used "Private Window" to reproduce this.

Can we mark this as "RESOLVED CONFIGURATION CHANGED", since it seems to be fixed in STP166.

[Ryosuke Niwa]

Yeah, this seems to be working now.