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

[whatwg] Spellchecking proposal #2

From: Matthew Raymond <mattraymond@earthlink.net>
Date: Mon, 26 Jun 2006 15:41:24 -0400
Message-ID: <44A03864.4080108@earthlink.net>
Anne van Kesteren wrote:
> Quoting Gervase Markham <gerv at mozilla.org>:
>> If this whole attribute rigmarole is merely about trying to distinguish
>> between an <input type="text"> containing email addresses and one
>> containing a subject line, then it seems like a storm in a teacup to me.
>> Either people have to manually request it for subject lines, or the
>> email addresses get red squiggly underlines - deal with it. :-)
> 
> So Google is using a <textarea> for email addresses.

   They can work around this by using the repetition features in Web
Forms 2.0:

| <table>
|  <tr id="order" repeat="template" repeat-start="1">
|   <td>
|    <select name="email[order].type">
|     <option>To:</option>
|     <option>Cc:</option>
|     <option>Bcc:</option>
|    </select>
|   </td>
|   <td>
|    <input type="text" name="email[order].address" pattern="[email]">
|   </td>
|   <td><button type="remove">Remove</button></td>
|  </tr>
| </table>
| <p><button type="add" template="order">Add Email Address</button></p>

   (Note: Replace "[email]" above with a valid pattern value for email.)

   Are email addresses common enough for an "email" type??? They seem
pretty common to me, but we might be overloading the |type| attribute a
bit if we add a new value that's so close to being text. Also, that
doesn't help the above scenario, because I think Google allows names
from an address book in the place of addresses.
Received on Monday, 26 June 2006 12:41:24 UTC

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