Anne van Kesteren wrote:
So I'm not sure about using CSS or XBL, but I do see a need coming
back where you can simple do:
foo { spellcheck:on; content:html-snippet }
... or something like that and have it globally declared for _every_
page that uses the property sheet instead of on
On Jun 24, 2006, at 17:02, Lachlan Hunt wrote:
I could easily imagine authors wanting to disable spell checking
simply because the squiggly red underlines clash with their site's
colour scheme.
One way to deal with that problem is to ship browsers with spell
checking turned off. Web
Quoting Matthew Raymond [EMAIL PROTECTED]:
So I'm not sure about using CSS or XBL, but I do see a need coming
back where you can simple do:
foo { spellcheck:on; content:html-snippet }
... or something like that and have it globally declared for _every_
page that uses the property sheet
Matthew Paul Thomas wrote:
On Jun 25, 2006, at 2:02 AM, Lachlan Hunt wrote:
...
However, the proposed spellcheck attribute has one major advantage
over all of those: it's being designed to allow the user to easily
override it if they want to.
But realistically, browsers won't allow the user
Hi, Ian,
I'd be happy without the attribute at all, but Mozilla is going to have
something to enable/disable this feature from markup, and they wanted to
have a spec for it so they asked WHATWG to provide a strawman. I figure
it's better to have a spec and an implementation than just an
Andrew Fedoniouk wrote:
Spellchecker looks like pure behavioral entity.
Behavior is generally handled exclusively by Javascript, but some
people have expressed that having to use script to enable spell checking
is highly undesirable.
So I would define this as:
style
#myeditor
{
On Sun, 25 Jun 2006 12:16:09 +0700, Matthew Paul Thomas [EMAIL PROTECTED]
wrote:
But realistically, browsers won't allow the user to easily override it
if they want to, because any interface for doing that would be absurd.
Not necessarily.
Check spelling:
( ) Never
(*) As the page author
