- From: <bugzilla@jessica.w3.org>
- Date: Thu, 23 Feb 2012 20:43:04 +0000
- To: public-webapps@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16094 Summary: Do not allow editing commands to affect editing hosts that aren't near the selection Product: WebAppsWG Version: unspecified Platform: All OS/Version: All Status: NEW Severity: normal Priority: P2 Component: HTML Editing APIs AssignedTo: ayg@aryeh.name ReportedBy: ayg@aryeh.name QAContact: sideshowbarker+html-editing-api@gmail.com CC: mike@w3.org, public-webapps@w3.org (In reply to bug 13118 comment #20) > I think similar problems can arise with selections spanning non-nested editing > hosts, or outside of editing hosts entirely. E.g., per current spec, running > "indent" on > foo<div style=display:inline contenteditable=true>bar</div>[baz] > will actually produce > foo<div style=display:inline > contenteditable=true><blockquote>bar</blockquote></div>[baz] > or something, I think. This is probably just a spec bug, though! Probably > block-extending the selection shouldn't cross editing hosts. > > So we should try to make sure that commands don't affect any editing hosts that > aren't ancestors of some node that's contained or partially contained in the > selection? This should be changed. If the selection doesn't touch an editing host, commands should never affect it. Likewise, if multiple beforeInput events get fired at different editing hosts, canceling some should make the command not affect that editing host. -- Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
Received on Thursday, 23 February 2012 20:43:06 UTC