2008/12/31 timeless <span dir="ltr"><<a href="mailto:timeless@gmail.com">timeless@gmail.com</a>></span><br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="Ih2E3d">On Tue, Dec 30, 2008 at 5:20 PM, Kornel Lesiński <<a href="mailto:kornel@geekhood.net">kornel@geekhood.net</a>> wrote:<br>
> It's useful for fields that contain non-textual content, e.g. product ID,<br>
> license plate "number", CAPTCHA answer, etc.<br>
> Browser would mark these as misspelt, which might be confusing or at least<br>
> distracting.<br>
<br>
</div>this sounds like something browser vendors need to worry about on<br>
their own and is not a reason to let web pages do anything about it.<br>
</blockquote></div><br>The browser can't know ahead of time that a text field is not supposed to contain natural-language text.<br clear="all"><br>Rob<br>-- <br>"He was pierced for our transgressions, he was crushed for our iniquities; the punishment that brought us peace was upon him, and by his wounds we are healed. We all, like sheep, have gone astray, each of us has turned to his own way; and the LORD has laid on him the iniquity of us all." [Isaiah 53:5-6]<br>