14636 2007-07-17 03:00:44 -0700 REGRESSION: broken tags with unpaired quote prevents encode autodetection 2010-10-15 13:13:36 -0700 1 1 1 Unclassified WebKit Page Loading 523.x (Safari 3) All All NEW http://developer.apple.com/jp/ HasReduction, InRadar, Regression P1 Major --- 1 808caaa4.8ce9.9cd6c799e9f6 webkit-unassigned ap darin ddkilzer dimich emacemac7 ian oldest_to_newest 4551 0 808caaa4.8ce9.9cd6c799e9f6 2007-07-17 03:00:44 -0700 // derived from bugs#14601 With some broken meta tags like: > <meta http-equiv="Content-Type" content="text/html; charset="utf-8"> detectJapaneseEncoding() seems to not to be called. For not-collectly-paired \x22, checkForHeadCharset() lost sync for quote and runs out whole the content absorbed with returns-false (at 'if(ptr == pEnd) return false;' line 588). Tag/content may not contain linefeeds with almost websites. I think successfully aborting at scanning quote pair when linefeed occuered is with reality. My experimental code. ----- while (ptr != pEnd && *ptr != quoteMark) { if(*ptr=='\r' || *ptr=='\n'){ // too long tag content : may lost sync // successfully bail out m_checkedForHeadCharset = true; return true; } ++ptr; } ----- 4552 1 ap 2007-07-17 04:00:18 -0700 This is a regression from shipping WebKit, upgrading to P1. See <http://www.whatwg.org/specs/web-apps/current-work/#get-an> - if I'm reading it correctly, we are not supposed to honor such a META. Which might mean that we need to suggest a correction to the HTML5 algorithm. Also, I'm not sure why Firefox works - it's possible that it ignores the META, and auto-detects the encoding based on page text analysis. 4518 2 ddkilzer 2007-07-17 08:27:30 -0700 *** Bug 14643 has been marked as a duplicate of this bug. *** 4519 3 ddkilzer 2007-07-17 08:29:01 -0700 <rdar://problem/5340161>