Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Example login page misleading #32

Open
jw35 opened this issue Feb 7, 2013 · 1 comment
Open

Example login page misleading #32

jw35 opened this issue Feb 7, 2013 · 1 comment
Labels

Comments

@jw35
Copy link

jw35 commented Feb 7, 2013

The example login page in the style guide at

http://www.websupport.cam.ac.uk/Project-Light/template-variants/login-form.html

was never completed, but it has a major bug if anyone uses it: the fields are only identified by place holder text, and MSIE doesn't render place holder text. The standard also advises against identifying fields only by place holder.

The example should be removed, or the use of place holder text revised, or at least a note should be added.

@barneybrown
Copy link
Contributor

Thanks,

I'll get the example removed for now. This was a template requested by UCS anyway for the Raven login screen.

If we get requests for something similar in the future we can rework it.

Barney

From: jw35 <[email protected]mailto:[email protected]>
Reply-To: cambridgeuniversity/Project-Light <[email protected]mailto:[email protected]>
Date: Thursday, 7 February 2013 09:34
To: cambridgeuniversity/Project-Light <[email protected]mailto:[email protected]>
Subject: [Project-Light] Example login page misleading (#32)

The example login page in the style guide at

http://www.websupport.cam.ac.uk/Project-Light/template-variants/login-form.html

was never completed, but it has a major bug if anyone uses it: the fields are only identified by place holder text, and MSIE doesn't render place holder text. The standard also advises against identifying fields only by place holder.

The example should be removed, or the use of place holder text revised, or at least a note should be added.


Reply to this email directly or view it on GitHubhttps://github.com//issues/32.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants