[whatwg] <input type="text" accept="">

[Lachlan Hunt]

L. David Baron wrote:
> We might want to use the accept attribute in the future to indicate what
> types of content can be sent, and thus what types of input the user
> agent should allow.  Overloading that to get a boolean for whether
> spellchecking should be enabled seems broken.

AIUI, the accept attribute is just describing what type of input to 
allow.  In this example, when text/plain is specified, the UA has just 
automatically determined that spell checking would be helpful for the 
user.  Similarly, if text/html, application/javascript or */*+xml were 
specified, the browser could provide syntax checking.

I don't think the spec should explicitly define type="text/plain" as 
meaning UAs should provide spell checking, it can just provide that as 
an example of something a UA can do with it.

What should the UA do with accept="text/plain;charset=X", where X is 
some charset that potentially differs from the page's encoding?

e.g. if the page were served as text/html;charset=UTF-8 and contained
<input type="text" accept="text/plain;charset=ISO-8859-1">

Then how would that interact with <form accept-charset="X">?

-- 
Lachlan Hunt
http://lachy.id.au/