W3C home > Mailing lists > Public > www-style@w3.org > December 2010

Re: Implementing contentEditable in CSS3 UI

From: Benjamin Hawkes-Lewis <bhawkeslewis@googlemail.com>
Date: Mon, 20 Dec 2010 21:59:44 +0000
Message-ID: <AANLkTimtZ0PQytTAPz8EkpR_cA2zWiab3ssyuPWQvvwO@mail.gmail.com>
To: Charles Pritchard <chuck@jumis.com>
Cc: tantekc@microsoft.com, www-style list <www-style@w3.org>
On Mon, Dec 20, 2010 at 7:14 PM, Charles Pritchard <chuck@jumis.com> wrote:
> Did the appearance properties get taken up by vendors?

https://developer.mozilla.org/en/CSS/-moz-appearance

>> Likewise, a single property to enable/disable spellcheck would be
>> preferable to some properties to tweak colors/decoration since that
>> could easily leave the display out of sync with behavior (e.g. screen
>> readers like VoiceOver would still announce spelling errors, if you
>> clicked on a spelling error Safari would still give you a list of
>> spelling corrections).
>>
>
> When you bring up a property, do you mean a CSS property, or sticking with
> the current html 5 draft?

I meant CSS (though without deprecating "spellcheck").

> *[spellcheck=true] {
>  invalid-spelling: inherit | none | ...
> }

<bikeshed>

Maybe more like:

[spellcheck=true] {
    spell-check : inherit | yes | no ;
    grammar-check : inherit | yes | no;
}

</bikeshed>

--
Benjamin Hawkes-Lewis
Received on Monday, 20 December 2010 22:00:20 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:20:35 GMT