W3C home > Mailing lists > Public > whatwg@whatwg.org > June 2006

[whatwg] Spellchecking proposal #2

From: Matthew Raymond <mattraymond@earthlink.net>
Date: Sun, 25 Jun 2006 23:39:20 -0400
Message-ID: <449F56E8.5030309@earthlink.net>
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
> {
>     white-space:pre; overflow: auto; ...
>     behavior: textarea spellchecker;   /* textarea editor and spellchecker 
> */
> }
> </style>
> 
> In htmlayout engine each DOM element can have
> multiple behaviors assigned, so following:
> 
> <textarea id="myeditor">...</textarea>
> 
> will behave as a text area editor with spellchecker using
> style declaration above.
> 
> (in fact behavior:textarea and/or spechecker can be assigned to
> any DOM element with display-role: block, (not only textarea)
> but this is another story)

   This looks a lot like an HTML Control (HTC), but it's incorrect if it
is. Remember that binding mechanisms like HTC and XBL are for binding
HTML/CSS/Javascript to elements, so any solution provided by those
mechanisms would have to have support in one of those languages.

   However, I suspect this is supposed to be a means of using canned
styles built into the browser. While this may be useful is some cases,
there is a danger that this could lead to people trying to reimplement
(X)HTML using CSS/XBL.
Received on Sunday, 25 June 2006 20:39:20 UTC

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