- From: <bugzilla@jessica.w3.org>
- Date: Thu, 28 Jul 2011 18:29:02 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13424 Aryeh Gregor <Simetrical+w3cbug@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |Simetrical+w3cbug@gmail.com --- Comment #1 from Aryeh Gregor <Simetrical+w3cbug@gmail.com> 2011-07-28 18:29:01 UTC --- I use the following definitions right now: "An editing host is a node that is either an Element with a contenteditable attribute set to the true state, or the Element child of a Document whose designMode is enabled." "Something is editable if it is a node which is not an editing host, does not have a contenteditable attribute set to the false state, and whose parent is an editing host or editable." An important note in my spec: "Barring bugs, the algorithms here will not alter the attributes of a non-editable element; will not remove a non-editable node from its parent (except to immediately give it a new parent in the same editing host); and will not add, remove, or reorder children of a node unless it is either editable or an editing host. An editing host is never editable, so authors are assured that editing commands will only modify the editing host's contents and not the editing host itself." The idea of an editing host not being editable is that authors should be able to grab the innerHTML of the editing host and not have to worry that anything added attributes or whatnot (which some browsers do). Also, we want to make sure nothing is going to remove or relocate editing hosts themselves, only change their descendants. Another notable difference is that I allow any node to be editable, not just HTML elements. (Well, not Documents or DocumentFragments or DocumentTypes.) It's often important to know whether a text node or such is editable, and there's no reason the concept shouldn't apply to elements other than HTML elements. -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Thursday, 28 July 2011 18:29:03 UTC