input element in telephone state could have a specific style. I was thinking of adding a telephone icon at the right of the field to make it consistent with the searchbox element style. See bug 456229 for the search input. Alex, do you think it would be a good idea or you prefer to have no style at all ?
The Famfamfam icons (at http://www.famfamfam.com) might look good in forms. I don't know if we use them somewhere already, but they are in use on many websites and, I think I've seen them in Skype. Still, we probably should check if they are licensed in a way that prevents us from using them, and finally, we could always design our own if we want to, instead.
Err, two notes: * When I say forms, I mean fields. * The Famfamfam icons library have not been updated for a long time, but are still frequently downloaded. There are over a thousand icons we could benefit from using.
We create all of the icons for Firefox to match the platform that the user is on. Easy to do, just need to track all of the artwork that is going in so that we know about everything. People sometimes use famfamfam icons as placeholders until the new artwork is ready. A phone icon might not make the most sense for the field, odds are the person creating the form will have already provided a label or some other text on the page indicating that the use should enter a phone number, making the icon redundant. How does the telephone field operate, does it provide formating after the user starts to enter information, like () around the area code and - after the first three digits for an american number?
(In reply to comment #3) > We create all of the icons for Firefox to match the platform that the user is > on. Easy to do, just need to track all of the artwork that is going in so that > we know about everything. People sometimes use famfamfam icons as placeholders > until the new artwork is ready. Sounds good. > A phone icon might not make the most sense for the field, odds are the person > creating the form will have already provided a label or some other text on the > page indicating that the use should enter a phone number, making the icon > redundant. Considering these input-types are very new, they are also very rare to see in use. If an icon indication is placed by the browser itself, the newly created/modified won't have to do it themselves. This has the benefit of allowing the user to quickly see what the field is meant for, without even needing to read the label. > How does the telephone field operate, does it provide formating after the user > starts to enter information, like () around the area code and - after the first > three digits for an american number? The optional "punctuation", was discussed in bug 557620. The conclusion was that formating should be left to the serverside part, hopefully reducing confusion.
Is there a complete list of the field types that we are adding, I want to think about the icons for all of them.
https://wiki.mozilla.org/User:Mounir.lamouri/HTML5_Forms should cover all of them, I think. Volkmar? It also shows progress on our implementation of them (the functionality, not necessarily the look/UI)
Ok great. Eventually for a lot of these we will likely want to provide autocomplete when some of the contacts stuff from labs makes it in: http://mozillalabs.com/blog/2010/03/contacts-in-the-browser/ (so for instance the telephone field can autocomplete with phone numbers, etc.) Do we have a meta bug to track all of the UI changes created yet?
Basically I would like to put together a spec that covers all of the HTML5 form controls, and have the rest of the UX team look over it and comment in a meta bug, then we can spin off the work into individual bugs like this one.
(In reply to comment #7) > Do we have a meta bug to track all of the UI changes created yet? I'm pretty sure no such meta bug exists yet, but having one sounds like a good idea.
Summary: Input element telephone state style → Style for <input type="tel">
Bug 557620 Comment 26 gave me an idea. Instead of doing any formating of the input (adding splitters etc), perhaps we could use a different font to illustrate that the field isn't normal? And, this will be overide-able through the font and font-family properties for the site author.
fonts are generally consistent across the platform, so this could potentially make the field feel different in a bad way. Also the font will only be displayed after the user has started to provide input, at which point the auto complete or any applied structure (like adding parenthesis around the are code) will serve as a strong indicator that the field is different.
I figured, a good way of making these fields accessible and add something special to an input in the telephone state at the same time, could be to ship tiny sound-files containing the sounds heard when you press keys on a normal phone. Thus, when a person enters "1" in an telephone-input field, we play a sound that corresponds to pressing "1" on a normal phone. I am pretty sure that we can find non-patented versions of these sounds (so that we are allowed to ship them). There is also a bug (bug 559746) filed to make the telephone state accessible. Surely the idea behind having these sounds in normal phones is to allow blind people to make sure that they have pressed the correct button on the keypad? The advantages and disadvantages, that I can see, are as follows: Advantages: * Separates the phone-fields from other fields * Introduces sounds to Firefox, hopefully received as a positive surprise by users. * Is very useful for people who need these fields to be more accessible (blind). Disadvantages: * Could be considered annoying. But considering how rarely you encounter a field where you type a phone number on the Internet, it will, in all likeliness not be often enough to annoy people. * Increases file-size. This, we can't escape, but depending on which format we choose, I believe that they can become small enough to not even be seen on the general size of the Firefox download. Fun and accessible or annoying and file-size increasing. What do you think?
^ Reading my older comments on the Bugzilla is embarrassing. You can ignore the above, as I realize the suggestion I put forth may be pushing it to the extreme. I trust the accessibility team to come up with something for those who need it, without my silly suggestions.
You need to log in before you can comment on or make changes to this bug.