W3C home > Mailing lists > Public > whatwg@whatwg.org > January 2007

[whatwg] contenteditable="" values and isContentEditable

From: Jorgen Horstink <mail@jorgenhorstink.nl>
Date: Fri, 19 Jan 2007 23:36:57 +0100
Message-ID: <5C5E6A11-ACFA-4B97-AB0B-04CF1FE078EB@jorgenhorstink.nl>
I second Anne's opinion about a new attribute isContentEditable. Both  
Internet Explorer and Safari have implemented this already although  
Safari's support for inherit has a few bugs. It really is needed for  
compatibility.

The empty string indeed causes the element to be contentEditable in  
both IE and Safari. I'd suggest to make the element editable if the  
attribute value has the empty string.


On Jan 19, 2007, at 10:51 PM, Anne van Kesteren wrote:

> The following would match Internet Explorer (and Opera's current  
> implementation):
>
>  - The empty string
>  - "true" (case-insensitive match)
>    -> Content of the element is editable.
>
>  - "false" (case-insensitive match)
>    -> Content of the element is *not* editable.
>
>  - Any other value
>    -> Equivalent to not specifying the attribute.
>
> This is based on some tests I made last year http:// 
> dump.testsuite.org/2006/contenteditable/ to find out what we had to  
> do in Opera.
>
>
> I think it would also be a good idea to add the isContentEditable  
> DOM attribute to HTMLElement as it needs to be supported for  
> compatibility and it allows you to find out whether or not an  
> element is editable when the contenteditable attribute is not  
> directly specified on it (but on an ancestor element).
>
>
> -- 
> Anne van Kesteren
> <http://annevankesteren.nl/>
> <http://www.opera.com/>
>
Received on Friday, 19 January 2007 14:36:57 UTC

This archive was generated by hypermail 2.3.1 : Monday, 13 April 2015 23:08:31 UTC