- From: Ian Hickson <ian@hixie.ch>
- Date: Fri, 10 Jul 2009 05:28:31 +0000 (UTC)
- To: Peter Kasting <pkasting@google.com>, Simon Pieters <simonp@opera.com>
- Cc: public-html <public-html@w3.org>
On Thu, 11 Jun 2009, Peter Kasting wrote: > On Thu, Jun 11, 2009 at 5:06 PM, Ian Hickson <ian@hixie.ch> wrote: > > On Wed, 27 May 2009, Simon Pieters wrote: > > > > > > .contentEditable is of type DOMString which supports the values > > > "true", "false" and "inherit". .spellcheck is a boolean attribute. > > > It would be nice if these two were aligned so that .spellcheck = > > > 'inherit' removes the content attribute. > > > > My understanding is that there are already implementations of this, > > and that there are pages that use it. Do people think this is > > important enough to change this regardless? Input from people who are > > more familiar with the deployment of this feature would be helpful. > > The semantics of "inherit" wouldn't break things, I don't know if > changing from a boolean to a DOMString would break script though. On Fri, 12 Jun 2009, Simon Pieters wrote: > > contentEditable was actually a boolean in Opera until not so long ago. > > The change shouldn't break existing content or legacy implementations > when true and false are used. New content that uses 'false' or 'inherit' > will get the wrong value in legacy implementations, though. Ok, I changed spellcheck to be a DOMString attribute with values "true", "false", and "default" (not "inherit" since it's not quite the same as contenteditable here). This means you can't find what the default state anymore, but I'm not sure that was that useful anyway. -- Ian Hickson U+1047E )\._.,--....,'``. fL http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
Received on Friday, 10 July 2009 05:29:09 UTC