This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Validtor's XHTML is served as text/html, even to XHTML browsers. If proper XML Content-Type is forced, the scripts cease to work: options aren't hidden initially, there are no DHTML effects. (forgive me not telling exactly why - the amount and complexity of script used for this simple effect is disheartening)
(In reply to comment #0) > If proper XML Content-Type is forced, the scripts cease to work: Indeed, it looks like the mootools libraries are using document.write, which won't work with XML. Forwarding the feedback. > options aren't hidden initially, there are no DHTML effects. But the interface does degrade "gracefully" when scripting is disabled or not working.
(In reply to comment #1) > > But the interface does degrade "gracefully" when scripting is disabled or not > working. I'll have to disagree to some extent here. http://lists.w3.org/Archives/Public/www-validator/2007Jun/0014.html Even if Firefox 1.5.0.12 is probably the last one in the 1.5 series, it's not that old, and moreover I'm not sure if I understand the benefit of the "smooth transition/fading" effects for the validator's UI in the first place.
(In reply to comment #2) > (In reply to comment #1) > > > > But the interface does degrade "gracefully" when scripting is disabled or not > > working. > > I'll have to disagree to some extent here. > http://lists.w3.org/Archives/Public/www-validator/2007Jun/0014.html That's apparently a CSS problem, we're looking at it.
(changing milestone, making sure we don't overlook this before releasing 0.8.0)
The main scripting issues are fixed, and the mootools team is aware that the usage of document.write() is problematic - there is only one left in the library at the moment. Keeping this open, to track in future.