This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 20421 - It is not entirely clear what the behavior for elements with contentEditable="false" should be.
Summary: It is not entirely clear what the behavior for elements with contentEditable=...
Status: RESOLVED FIXED
Alias: None
Product: WHATWG
Classification: Unclassified
Component: HTML (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: Unsorted
Assignee: Ian 'Hixie' Hickson
QA Contact: contributor
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-12-18 02:36 UTC by contributor
Modified: 2013-03-05 00:45 UTC (History)
3 users (show)

See Also:

Attachments

Description contributor 2012-12-18 02:36:54 UTC 
Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/editing.html
Multipage: http://www.whatwg.org/C#spelling-and-grammar-checking
Complete: http://www.whatwg.org/c#spelling-and-grammar-checking

Comment:
It is not entirely clear what the behavior for elements with
contentEditable="false" should be. 

Posted from: 74.125.59.185 by groby@google.com
User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_2) AppleWebKit/537.22 (KHTML, like Gecko) Chrome/25.0.1363.0 Safari/537.22
Comment 1 Ian 'Hixie' Hickson 2012-12-31 04:57:58 UTC 
Does this specification clarify things, or is it still ambiguous?
   http://dvcs.w3.org/hg/editing/raw-file/tip/editing.html

If it's still ambiguous, please let me know what exactly is ambiguous, because I can't work out what possible behaviours you have in mind as being possibly allowed that shouldn't be.
Comment 2 Rachel Blum 2013-03-05 00:45:07 UTC 
I wish I recalled... I believe I wasn't entirely clear on textareas with contentEditable=false, but that's covered by the Text node case. Marking resolved.