On Mon, 2 Aug 2010, Dirk Pranke wrote:
On Mon, Aug 2, 2010 at 6:12 PM, Ian Hickson i...@hixie.ch wrote:
This thread primarily discussed ways to allow users to log in and out
of sites, possibly through improvements to the forms model.
This is an area that seems to be under a lot of
This thread primarily discussed ways to allow users to log in and out of
sites, possibly through improvements to the forms model.
This is an area that seems to be under a lot of active research, so it's
probably premature to change the HTML spec at this point. I haven't
introduced any new
On Mon, Aug 2, 2010 at 6:12 PM, Ian Hickson i...@hixie.ch wrote:
This thread primarily discussed ways to allow users to log in and out of
sites, possibly through improvements to the forms model.
This is an area that seems to be under a lot of active research, so it's
probably premature to
I think using the role attribute is the best solution here:
input type=text role=username
input type=email role=username
This way we're using the type attribute to indicate what sort of data
is being entered, and the role attribute to indicate how it will be
used. I think the separation of these
The way I see it is that instead of browsers traversing the DOM looking
for
an input field of either id=username or name=username or even
class=username, they now only have to look for an input of type username.
Makes it a lot easier for both developers and browser vendors as they now
only
: Schalk Neethling; WHATWG List; Steve Dennis
Subject: Re: [whatwg] RFC: input type=username
On Thu, May 6, 2010 at 11:51 AM, Markus Ernst derer...@gmx.ch wrote:
Am 05.05.2010 23:06 schrieb Schalk Neethling:
The way I see it is that instead of browsers traversing the DOM
looking for an input field
On Thu, May 6, 2010 at 12:12 PM, Mounir Lamouri wrote:
On 05/06/2010 12:09 PM, Thomas Broyer wrote:
On Thu, May 6, 2010 at 11:51 AM, Markus Ernst derer...@gmx.ch wrote:
Am 05.05.2010 23:06 schrieb Schalk Neethling:
The way I see it is that instead of browsers traversing the DOM looking
for
On Thu, 2010-05-06 at 14:54 +0200, Thomas Broyer wrote:
On Thu, May 6, 2010 at 12:12 PM, Mounir Lamouri wrote:
On 05/06/2010 12:09 PM, Thomas Broyer wrote:
On Thu, May 6, 2010 at 11:51 AM, Markus Ernst derer...@gmx.ch wrote:
Am 05.05.2010 23:06 schrieb Schalk Neethling:
The way I see
Schalk Neethling writes:
if your username field will be in the form of an email address, then
simply use type=username with a pattern to facilitate email
validation.
Surely a major reason for having standard validation types is so web
developers don't need to come up with patterns for these
Of Smylers
Sent: Thursday, May 06, 2010 3:18 PM
To: whatwg@lists.whatwg.org
Subject: Re: [whatwg] RFC: input type=username
Schalk Neethling writes:
if your username field will be in the form of an email address, then
simply use type=username with a pattern to facilitate email
validation
On 5/4/10 12:08 AM, Eitan Adler wrote:
3) Currently autofill for usernames looks for something like
id=username or name=username. However on certain websites this
fails. Furthermore some websites offer a find other members feature
where you could type in a username. I've often seen these fields
On Tue, May 4, 2010 at 8:21 PM, Boris Zbarsky bzbar...@mit.edu wrote:
On 5/4/10 10:56 PM, Dirk Pranke wrote:
What I would like to offer is a way to control some amount of the
sign-in/sign-out
experience while improving the security, by at least giving an in-page
way to trigger sign-in /
Eitan Adler:
A type=username is added to the input element. type=username would MUST
only be used for the name that is used to log in to the site. It MUST NOT be
used for registration forms or anything else that requires a username. A form
MAY have up to one (but not more) type=username
05, 2010 8:20 AM
To: Boris Zbarsky
Cc: whatwg@lists.whatwg.org
Subject: Re: [whatwg] RFC: input type=username
On Tue, May 4, 2010 at 8:21 PM, Boris Zbarsky bzbar...@mit.edu wrote:
On 5/4/10 10:56 PM, Dirk Pranke wrote:
What I would like to offer is a way to control some amount of the
sign
On 5/05/2010, at 9:09 PM, Christoph Päper wrote:
Eitan Adler:
A type=username is added to the input element. type=username would MUST
only be used for the name that is used to log in to the site. It MUST NOT be
used for registration forms or anything else that requires a username. A
To: Christoph Päper
Cc: WHATWG List
Subject: Re: [whatwg] RFC: input type=username
On 5/05/2010, at 9:09 PM, Christoph Päper wrote:
Eitan Adler:
A type=username is added to the input element. type=username would
MUST only be used for the name that is used to log in to the site. It MUST
NOT be used
Use cases:
1) A screen reader that sees a form with a type=username and a
password field. The screen reader could just ask Log in to this site?
[y/n]?. No further context would be needed.
2) UAs can more easily discover login forms and offer things such as
Firefox's Account Manager [1] or a
On Tue, May 4, 2010 at 10:08 AM, Eitan Adler eitanadlerl...@gmail.com wrote:
3) Currently autofill for usernames looks for something like
id=username or name=username. However on certain websites this
fails.
Why would a site which doesn't cooperate with today's autofill
features choose to
On 4/05/2010, at 9:07 AM, timeless wrote:
On Tue, May 4, 2010 at 10:08 AM, Eitan Adler eitanadlerl...@gmail.com wrote:
3) Currently autofill for usernames looks for something like
id=username or name=username. However on certain websites this
fails.
Why would a site which doesn't
On 4 May 2010, at 09:07, timeless wrote:
On Tue, May 4, 2010 at 10:08 AM, Eitan Adler eitanadlerl...@gmail.com wrote:
3) Currently autofill for usernames looks for something like
id=username or name=username. However on certain websites this
fails.
Why would a site which doesn't cooperate
I don't think type=username is good solution, but I agree that autofill needs
help. Sites often use e-mail address as login. There would be conflict
between type=email and type=username.
I could imagine one two solutions here. 1) Change type=username to
role=username which makes more sense
On Tue, May 4, 2010 at 2:02 PM, Jonas Sicking jo...@sicking.cc wrote:
On Tue, May 4, 2010 at 1:53 PM, Dirk Pranke dpra...@chromium.org wrote:
On Tue, May 4, 2010 at 12:08 AM, Eitan Adler eitanadlerl...@gmail.com
wrote:
Use cases:
1) A screen reader that sees a form with a type=username and a
22 matches
Mail list logo
