[Bug 13416] New: Section 7.5, contenteditable attribute, should be renamed "editing host" and reworked

http://www.w3.org/Bugs/Public/show_bug.cgi?id=13416

           Summary: Section 7.5, contenteditable attribute, should be
                    renamed "editing host" and reworked
           Product: HTML WG
           Version: unspecified
          Platform: PC
        OS/Version: All
            Status: NEW
          Severity: major
          Priority: P2
         Component: HTML5 spec (editor: Ian Hickson)
        AssignedTo: ian@hixie.ch
        ReportedBy: schwer@us.ibm.com
         QAContact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-wg-issue-tracking@w3.org,
                    public-html@w3.org


Section 7.5 should be renamed "editing host" or something like that as the name
implies the section only applies to the contenteditable attribute. The section
should be reworked.

    Where it becomes confusing is designMode. designMode places the entire
document in an editing mode and should also be considered an editing host.
    DesignMode (section 7.5.2) is a subsection of 7.5, the contenteditable
attribute. Yet, 7.5.1 defines User Editing Actions. It is not clear that User
Editing Actions apply to both contenteditable and designMode. I think we agree
that it should and it is intended but that is now how section 7.5 is
structured. Where this becomes important is that 7.5.1 describes the user
functions apply to an editing section. This is important for main stream
clarification and for accessibility to ensure access to Editing Hosts. These
also need to apply to designMode. Fortunately, the user functions (move the
caret, etc.) are defined in a device independent way. 7.5 should be
restructured as follows: 

7.5 Editing hosts

Introductory text should state that this applies to elements having
contentEditable in the true state and design Mode in the enabled state.

7.5.1 contentEditable 7.5.2 designMode 7.5.3 User Editing Actions for Editing
Hosts

Another approach could be to state that designMode="on" means the equivalent of
"contentEditable" being true as applied to the entire document. 

Where this becomes an accessibility problem is that people with disabilities
need consistency among editable sections of the document.

-- 
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 16:57:19 UTC