Jump to content

Is 'Password' a reserved term?


TomTees

Recommended Posts

Is 'password' a protected/resevred term in either PHP or HTML?

 

Is this code valid...

 

<li>

<label for="password">

<em><img src="images/required.png" alt="required" /></em>

Password:

</label>

<input id="password" name="password" class="text" type="password" />

</li>

 

 

 

TomTees

 

 

Link to comment
Share on other sites

No. Why are you asking?

 

Ken

 

Because it seems to me that the author of a PHP book I read said it was and so he always used "pass1" and "pass2" on his forms.  (Or so I recall?!)

 

 

TomTees

 

 

 

@tomtees; I'm intrigued about this 'trick', what exactly does it achieve, as I said, em is for manipulating text..

 

And WRT passwords, would it not be easier to assign a name to a textarea or input that's relevant to the context of the application your writing.. Seems like the easier way to go to me ;p

 

Rw

Link to comment
Share on other sites

@tomtees; I'm intrigued about this 'trick', what exactly does it achieve, as I said, em is for manipulating text..

 

My code actually needs to be updated since I changed the label alignment, but when the labels were left aligned, I need <em>.

 

 

See this article about 3/4 the way down...

 

http://articles.sitepoint.com/print/fancy-form-design-css

 

 

And WRT passwords, would it not be easier to assign a name to a textarea or input that's relevant to the context of the application your writing.. Seems like the easier way to go to me ;p

 

Rw

 

I have no clue what you are saying?!

 

I used a text field to gather the password.  Why would you use anything else?!

 

 

TomTees

 

 

Link to comment
Share on other sites

Well instead of <input type="password" name="password" /> you could have something like <input type="password" name="AdminPassword" /> or <input type="password" name="LoginPassword" />

 

Purely something to distinguish any ambiguity if your coding lots of things, it just makes the context of what your programming easier to work with and semantically speaking, makes things easier to read if your code is split up in OOP structure.

 

Cheers for the link, good read...

 

Rw

Link to comment
Share on other sites

Well instead of <input type="password" name="password" /> you could have something like <input type="password" name="AdminPassword" /> or <input type="password" name="LoginPassword" />

 

Purely something to distinguish any ambiguity if your coding lots of things, it just makes the context of what your programming easier to work with and semantically speaking, makes things easier to read if your code is split up in OOP structure.

 

Okay, I follow what you are saying now.

 

 

Cheers for the link, good read...

 

Rw

 

Yeah, if you want to become an expert on CSS Forms, that is one of the better articles/tutorials out there.  That and it also takes in to account Accessibility which is always good!

 

Happy reading,

 

 

 

TomTees

 

Link to comment
Share on other sites

This thread is more than a year old. Please don't revive it unless you have something important to add.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.