16621 2007-12-27 00:36:02 -0800 WebKit ignores encoding description in invalid HTML if it's too far from the start 2024-06-01 17:10:52 -0700 1 1 1 Unclassified WebKit Page Loading 528+ (Nightly build) Mac OS X 10.4 NEW P2 Normal --- 1 ap webkit-unassigned ahmad.saleem792 darin ddkilzer ian jshin mrowe oldest_to_newest 65350 0 ap 2007-12-27 00:36:02 -0800 From bug 12526 comment 3. Our heuristic for <meta> charset declarations differs from what Firefox does, and what is documented in HTML5. Namely, we do not check for <meta> during normal parsing and re-start parsing if the charset changes late in the game. We only pre-parse the first 512 bytes of the document, or the whole <head>, whichever is larger. This is usually enough, but we know of pages that aren't decoded correctly because of this difference. The following two pages have a very long script (~ 10kB) at the beginning, and charset declaration in <meta> is not honored. http://db66.vnet.cn/ http://www.ddm.com/event/event84.asp?code=-548 Restarting parsing at any point is a big can of worms though - e.g., some scripts with side effects may run twice because of that. 65372 1 mrowe 2007-12-27 01:58:44 -0800 Is the handling of scripts when reparsing discussed in the HTML5 specification? Is that something which should be documented in the spec? 65384 2 ap 2007-12-27 02:28:56 -0800 See <http://www.whatwg.org/specs/web-apps/current-work/#change>. 66602 3 ian 2008-01-08 18:37:00 -0800 (basically, HTML5 requires that the scripts run twice.) 2039286 4 ap 2024-06-01 17:10:52 -0700 *** Bug 275017 has been marked as a duplicate of this bug. ***