W3C home > Mailing lists > Public > public-webapps@w3.org > January to March 2012

[Bug 16095] New: Element with contenteditable=true shouldn't be considered as an editing host if it's already in an editable region

From: <bugzilla@jessica.w3.org>
Date: Thu, 23 Feb 2012 22:00:05 +0000
To: public-webapps@w3.org
Message-ID: <bug-16095-2927@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16095

           Summary: Element with contenteditable=true shouldn't be
                    considered as an editing host if it's already in an
                    editable region
           Product: WebAppsWG
           Version: unspecified
          Platform: PC
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: HTML Editing APIs
        AssignedTo: ayg@aryeh.name
        ReportedBy: rniwa@webkit.org
         QAContact: sideshowbarker+html-editing-api@gmail.com
                CC: mike@w3.org, public-webapps@w3.org


This is a request to match the original HTML5 spec definition of the editing
host.

Elements with contenteditable=true shouldn't define a new editing host unless
the element is in a non-editable region (i.e. it doesn't have an editing host
of its own). This matches the way CSS inheritance and computed value works.

WebKit can't implement the current definition of editing host since we use CSS
style resolver to decide whether a given element is an editing host or not.

-- 
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 22:00:08 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:50 GMT