9650 2010-05-03 22:48:50 +0000 WHATWG Spec Web Site Freeze 2010-10-04 14:32:41 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML5 spec (editor: Ian Hickson) unspecified PC Windows NT RESOLVED WORKSFORME http://www.whatwg.org/specs/web-apps/current-work/#the-input-element-as-domain-specific-widgets P2 normal --- 1 dhtmlkitchen ian dhtmlkitchen ian mike Ms2ger public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 35384 0 dhtmlkitchen 2010-05-03 22:48:50 +0000 The website of the editors draft is freezing Firefox. The freeze lasts for about 120 seconds (2 min). After being frozen, the various status notifications that are added to the page. When the page is loaded with javascript disabled, Firefox does not freeze. http://www.whatwg.org/specs/web-apps/current-work/#the-input-element-as-domain-specific-widgets The problem should be fixed so that users are not subjugated to having the browser taken over by javascript. Although unrelated, the page also frequently will display javascript errors, such as: | fixBrokenLink is not defined | [Break on this error] fixBrokenLink(); | Overview.html (line 281) I suggest instead "fixBrokenSite". 35466 1 Ms2ger 2010-05-06 15:11:21 +0000 Use <http://www.whatwg.org/specs/web-apps/current-work/?slow-browser> or a Firefox 3.7 build <http://www.mozilla.org/projects/devpreview/releasenotes/#download>. 35467 2 lachlan.hunt 2010-05-06 15:48:25 +0000 The problem here is this script. http://www.whatwg.org/specs/web-apps/current-work/status.js Use an ad blocker to manually block that script and you'll have no problem. Alternatively, if you have time, volunteer to rewrite that script so that it's not so inefficient. 36416 3 dhtmlkitchen 2010-06-24 21:51:56 +0000 Performing DOM traversal on page load is inherently inefficient. The larger the document, the more of a problem it will be. The problem only gets worse on slower machines and so testing it on a fast machine is not going to reveal much. Instead of trying to fix it; don't do DOM traversal onload at all. I see the resolution WORKSFORME. Does that mean the problem is solved by using a script blocker, as indicated in comment #2, or does it mean that the problem wasn't observable? When changing status, please provide a short comment for others to read - thanks.