Harlan said:
If you have
selected=selected
then the tag is invalid.
No it isn't.
If your document is meant to be HTML, then it
should just be
selected
No, selected=selected and selected="selected" and selected='selected' are
all permitted and equivalent in HTML up to and including HTML 4.01. Ref.:
the end of
http://www.w3.org/TR/html4/intro/sgmltut.html#h-3.3.4
(which is outdated, as browsers that only recognize the minimized form must
be really rare nowadays).
The shorthand that consists of the value selected only is often described as
being the attribute name without value, but by the SGML standard, and hence
formally in HTML up to and including HTML 4.01, it is the value of an
attribute. However, in this special case, the attribute value must not
appear in quotation marks. Rather confusing, isn't it?
This explains the oddity that in a <table> tag, the word border may appear
alone and it means frame="border". It's thus interpreted as the value of the
attribute that has this value as one of the possible enumerated values. In
principle, you could also use <table hsides rows> (try it on a validator if
you don't believe me) and it would mean <table frame="hsides" rules="row">
but don't expect browsers to grok it. In practice, browsers don't do SGML
parsing but some kludgery, which among other things deals with <table
If it's meant to be XHTML, then it needs to be
selected="selected"
Or selected='selected', to be exact.
I don't know if fixing that will solve your problem,
I don't think the problem has anything to do with the format of the
attribute used, or that attribute at all.
The problem is most probably in the code that was used to generate the
markup client-side via JavaScript, thereby exhibiting differences between
browsers. I might be stretching my crystal ball too much, but the error
seems to be at line 42 of the code. I might be wrong here of course. What is
fairly certain is that the URL is needed if the OP wants his problem solved
and not just enjoy our lectures (which are of course infinitely more
interesting than some casual boring practical authoring issue, in a context
where the whole approach is probably wrong).