in reply to Re^2: Passing 'SELECT MULTIPLE' parameters and CGI
in thread Passing 'SELECT MULTIPLE' parameters and CGI

In both instances it seems to have changed the order and set MULTIPLE to either "" or "multiple".

The value of multiple doesn't matter, just the presence or absence of the attribute.

  • Comment on Re^3: Passing 'SELECT MULTIPLE' parameters and CGI

Replies are listed 'Best First'.
Re^4: Passing 'SELECT MULTIPLE' parameters and CGI
by afoken (Chancellor) on Aug 17, 2010 at 20:17 UTC

    I think this is only true for HTML, but XHTML insists on having a value for multiple, and it must be multiple. The same applies to checked and other "no-value" attributes.

    Alexander

    --
    Today I will gladly share my knowledge and experience, for there are no sweeter words than "I told you so". ;-)

      The only difference is that XML (and thus XHTML) requires that you specify a value if you specify the attribute. XHTML does not impose any extra requirements on what the value is.

      It's must either be multiple="multiple" in both or in neither.

        XHTML does not impose any extra requirements on what the value is.

        It does, actually. See the DTD:

        <!ATTLIST select [...] multiple (multiple) #IMPLIED

        That defines the 'multiple' attribute as having an enumerated set of possible values. Though in this case, there's not much enumeration to the set :)

        EDIT: Actually, on re-reading, I guess I may just be agreeing with you...