[Webkit-unassigned] [Bug 114791] Contenteditable issues related to backspace handling

[bugzilla-daemon at webkit.org]

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





--- Comment #7 from Piotrek Koszuliński (Reinmar) <pkoszulinski at gmail.com>  2013-09-26 07:53:31 PST ---
> It appears to me that we almost need two modes: visual and semantic.

> It's impractical to satisfy both needs simultaneously.

I'm not sure if I understand. Excluding TC1 and TC2 which are not reproducible on Safari (they are only reproducible on Chrome, so I guess it's a Blink's thing only) - how're TC3 and TC4 "visible"? There's semantic broken (but that's mostly under the hood for non-technical end users), and even if some behaviour is broken, then... why forking? Why not fixing it?

For example - in the TC3 user deletes text, text gets removed - it's already correct for the user. What's broken is under the hood - there's no <strong> tag in the DOM, but when user starts typing again it's recreated. So, why is it recreated if there was nothing in the DOM and why isn't it <strong> again, but <b>? Non-technical users won't notice if this was fixed, but technical users will be pleased that weird span/font/b/i tags are not created.

The TC1 and TC2 are different though, because they heavily affect UX. For example, end users are reporting us that they find it strange that paragraph merged into header still looks like a paragraph. More technical ones also don't like the fact that there's span with inline styles created, because it completely breaks the cleanliness of the code. But fortunately it doesn't happen on Safari.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.