- From: Ian Hickson <ian@hixie.ch>
- Date: Wed, 29 Jul 2009 18:56:00 +0000 (UTC)
- To: Geoffrey Sneddon <gsneddon@opera.com>
- Cc: public-html@w3.org
On Thu, 16 Jul 2009, Geoffrey Sneddon wrote: > Currently the spec. says, for element.spellcheck: > > > On setting, if the new value is an ASCII case-insensitive match for the > > string "default" then the content attribute must be removed, if the new > > value is an ASCII case-insensitive match for the string "true" then the > > content attribute must be set to the string "true", if the new value is an > > ASCII case-insensitive match for the string "false" then the content > > attribute must be set to the string "false", and otherwise the attribute > > setter must raise a SYNTAX_ERR exception. > > As spellcheck is an enumerated attribute, states are ASCII > case-insensitive. Under my reading of the spec., this means upon setting > the DOM attribute to either "true" or "false" the content attribute must > be set to "true" or "false" respectively, case-insensitively. We > probably ought to define a case for it to be set to. The string "true" is in lowercase. If you read the spec as written, I believe this is unambiguous. -- Ian Hickson U+1047E )\._.,--....,'``. fL http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
Received on Wednesday, 29 July 2009 18:56:37 UTC