[Webkit-unassigned] [Bug 93583] Select/insertHTML at element boundaries inserts content in the wrong place

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=93583

--- Comment #7 from David Gatwood <dgatwood at mac.com> ---
If it is aligned with the spec, then the spec is badly broken.  The current behavior makes a lot of useful editing behavior impossible, and that's not good.

For background on this, I was trying to construct some semi-WYSISYG structured XML editors (for writing novels and screenplays) using WebKit, and I just plain gave up because I couldn't insert nodes inside empty elements, I couldn't reliably insert nodes between elements, I couldn't put the insertion cursor between elements even with element boundaries visible, etc.

If element boundaries are visible (with ::before and ::after pseudo-elements), then all of these locations (between elements, inside elements, etc.) are visually distinct locations in the document, and should absolutely not be canonicalized into a single position.

And the same is true for buttons.  No reasonable person would expect inserting content after a button to insert it into the button.  The inside of a button is visually distinct from the outside of a button.

So the current canonicalization behavior makes no sense.  It may be expected based on the way things are written right now, but it certainly isn't expected.  :-)

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20220531/3a5ac09a/attachment.htm>