Hi,
At first, I thought this problem was because I updated to the nightly
build of 1/27.
Whereas before, my select1 (with appearance="full") labels appeared
correctly alongside the radio button in the browser, now they did not
appear.
I did a view source and the text was there, just not showing.
This was with Firefox 1.5
Tested IE 6, and the text did show.
So I reverted to the nightly build from 1/21, and now label text in my
forms showed in both Firefox and IE.
Then I remembered that when I did the update, I did something I hadn't
done for a few weeks.
I went in and did my customizations of the standard epilogue/theme
files.
So I did it again and the label text was no longer visible in Firefox.
The key difference appears to be that I forced the epilogue to output
xhtml1 instead of html4, which it does by default, even for Firefox.
With this change in, I get no radio label text visible.
Without this change, I can see the radio text label.
So I pasted the source of the html sent to the browser into
validator.w3.org.
It fails, which would seem grounds for explaining the difference.
I went to the Orbeon site and the xforms-controls example that I had
been using as a guide.
I sent it (as html4) to the validator, and it failed - so it's not my
form that causes the problem.
I forced the validator to treat the page as xhtml, and it failed again.
Anyone got any ideas on
my original problem - missing text label on a radio when xhtml in
Firefox 1.5,
or why the epilogue produces html4 for Firefox,
or why it doesn't validate?
Today, exploring further, it would seem what Firefox and validator are
addressing is the idea that the input tag is specified as empty, and
OPS is putting the label text in there. For example
<input type="radio" name"xf-etc" value="yes">Yes</input>
should be more like
<input type="radio" name="xf-etc" value="yes"/><label
for="xf-etc">Yes</label>
or
<label for="xf-etc">Yes</label><input type="radio" name="xf-etc"
value="yes"/>
If I'm reading that right, anyway.
This is now happening I assume inside Java code rather than xsl.
It seems to me that should anyone be able to recode this to conform to
the spec, then it also needs to look at the xforms source and put the
label before or after the radio, as per the source. (At the moment, it
is defaulting to after, which happily is what I have in my source).
Thanks & regards
Colin
--
You receive this message as a subscriber of the
[hidden email] mailing list.
To unsubscribe: mailto:
[hidden email]
For general help: mailto:
[hidden email]?subject=help
ObjectWeb mailing lists service home page:
http://www.objectweb.org/wws
Locked
