RE: [PHP] Re: sloppiness & stupidity
| From: | Ford, Mike | Date: | Wed, 17 Jun 2009 09:18:09 +0000 |
| Subject: | RE: [PHP] Re: sloppiness & stupidity | ||
| References: | 1 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-294149@lists.php.net to get a copy of this message | ||
On 17 June 2009 02:11, Shawn McKenzie advised:
> PJ wrote:
>> I'm sorry, guys, but I am really getting po'd.
>> The irresponsible sloppiness and stupidity is just getting to me.
>> In my quest for a way to populate a multiple option select box I have
>> run across so many errors that it's beyond belief... such nonsense as
>> "select for select or select="select" ( think this is right, but then
>> who knows?)
>
> I know. So does the HTML recommendation which states that it is a
> boolean attribute, meaning it is stated (on/boolean 1) or it isn't
> (off/boolean 0) in the HTML context. So while other variations may
work,
> this is correct:
>
> For multiple select:
> <SELECT multiple name="component-select">
>
> --or--
>
> For single select:
> <SELECT name="component-select">
This is very true -- but XHTML requires *all* attributes to have a
value, so an XHTML conformant page will use <select multiple="multiple"
name="selector"> (or something similar such as <select multiple="yes"
name="selector">). The only inconsistency here is that different people
have chosen to validate against different standards.
Other differences you may see are because in most programming
TIMTOWTDI[1], as perl would have it, and different people make different
choices about which way to go.
Then again, some *is* simply due to sloppiness, or under-explanation
because of over-familiarity with the code or feature in question, or
confidence in one's own misunderstanding!
[1] There Is More Than One Way To Do It
Cheers!
Mike
--
Mike Ford, Electronic Information Developer,
C507, Leeds Metropolitan University, Civic Quarter Campus,
Woodhouse Lane, LEEDS, LS1 3HE, United Kingdom
Email: m.ford@leedsmet.ac.uk
Tel: +44 113 812 4730
To view the terms under which this email is distributed, please go to http://disclaimer.leedsmet.ac.uk/email.htm