Sent by Paul Novitski on 12 April 2010 18:06
> > I'd be happy to take a look, I'm always on the lookout for good
> > login scripts and I'd be happy to provide any feedback I can.
>
>
> > ONE*** This goes in the head section of the html page:
> > <script src="login.js" type="text/javascript"></script>
> >
> > TWO*** Then this form goes in the body section. You decide the
> content to include other than the form fields.
> > <form name="login" id="login">
....
> > <input type=button value="Login!" onClick="Login()" />
> > THREE*** The you create the "login.js" file from the following
> code. We have 13 different logins leading to thirteen different
> pages. Each one needs just 3 pieces of info: username, password and
> the page linked to.
This is not an appropriate topic for a CSS list.
This presentational markup desperately begs to be stripped bare and
replaced with nice clean semantic markup and a stylesheet.
Any form functionality that depends on JavaScript cannot be secure.
Write your security logic in a server-side script, then use
JavaScript if you want to enhance the user experience, but asking
JavaScript to be your gate-keeper is asking a narcoleptic to be your
nightwatchman.
Including JavaScript calls in markup is so '90s old-school it's
amazes me that people still code this way. Google separation of
development layers and progressive enhancement, please.
Croggled,
Paul
______________________________________________________________________
css-discuss [EMAIL-REMOVED]]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
List policies -- http://css-discuss.org/policies.html
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
