4619 2007-06-10 13:18:06 +0000 Validator's scripts work only in tagsoup mode 2018-05-09 20:10:39 +0000 1 1 1 Unclassified Validator Website 0.8.0b2 All All NEW http://validator-test.w3.org/ P2 normal 0.9.0 1 kornel ot www-validator-cvs oldest_to_newest 15342 0 kornel 2007-06-10 13:18:06 +0000 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) 15351 1 ot 2007-06-11 11:48:06 +0000 (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. 15357 2 ville.skytta 2007-06-11 16:08:33 +0000 (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. 15361 3 ot 2007-06-11 20:15:15 +0000 (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. 15389 4 ot 2007-06-12 20:21:18 +0000 (changing milestone, making sure we don't overlook this before releasing 0.8.0) 15843 5 ot 2007-07-18 06:25:49 +0000 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.