User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:5.0) Gecko/20100101 Firefox/5.0 Build Identifier: Mozilla/5.0 (Windows NT 5.1; rv:5.0) Gecko/20100101 Firefox/5.0 This site don't work in FF 4 and 5, click on cards does nothing. In versions 3.x.x it was good, in other browsers too. Url: http://taro.orakul.com Windows XP pro SP3. Safe mode do not help. Reproducible: Always Steps to Reproduce: 1. open http://taro.orakul.com 2. click on card deck must open card Actual Results: nothing happens, card still closed Expected Results: open card Intel Core2 Duo 2.4, RAM 2 Gb

Last good nightly: 2010-05-03 First bad nightly: 2010-05-04 Pushlog: http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=83c887dff0da&tochange=d6bb0f9e9519

Works for me. Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.9.2.17) Gecko/20110420 Firefox/3.6.17 Reproduced. Mozilla/5.0 (X11; Linux x86_64; rv:2.0.1) Gecko/20100101 Firefox/4.0.1 Mozilla/5.0 (X11; Linux x86_64; rv:5.0a2) Gecko/20110524 Firefox/5.0a2 Mozilla/5.0 (X11; Linux x86_64; rv:5.0) Gecko/20100101 Firefox/5.0 Mozilla/5.0 (X11; Linux x86_64; rv:7.0a1) Gecko/20110526 Firefox/7.0a1

Works for me with html5.parser.enable false in about:config. Mozilla/5.0 (X11; Linux x86_64; rv:2.0.1) Gecko/20100101 Firefox/4.0.1 Mozilla/5.0 (X11; Linux x86_64; rv:7.0a1) Gecko/20110526 Firefox/7.0a1 Thus, the regression is likely caused by: Bug 373864 - Enable the HTML5 parser by default.

Does not work either in: Opera 11.50.1015 Google Chrome 13.0.777.0 => Site Issue I presume, no?

There's some kind of problem in Subsys_JsHttpRequest_Js() in http://taro.orakul.com/js/http.js that makes req.onreadystatechange never get called in reqContent() in http://taro.orakul.com/js/script.js for FX4 and on. I also presume it's a site issue, but I actually don't know since it hasn't been fully tracked down.

Based on comment 3, over to parser.

I've seen this bit before elsewhere: span.innerHTML = 'Text for stupid IE.<s'+'cript></' + 'script>'; It assumes that it can run an innerHTML-inserted script if it manages to invoke an IE bug. However, HTML5 specced the general IE behavior--not the IE bug that's being relied on here.

The correct fix is to create the script element using document.createElement("script"), setting the URL and inserting the script to the DOM instead of creating the script element using innerHTML.

(In reply to comment #7) > I've seen this bit before elsewhere: > span.innerHTML = 'Text for stupid IE.<s'+'cript></' + 'script>'; Yes, we have it in bug 652333 also and a Google search gives about 50 hits with that dirty code.

Mozilla/5.0 (Windows NT 5.1; rv:13.0) Gecko/20100101 Firefox/13.0.1 seems to work now