116943 2013-05-29 01:44:14 -0700 Left arrow on NTP is corrupted 2013-08-09 22:30:56 -0700 1 1 1 Unclassified WebKit Page Loading 528+ (Nightly build) Unspecified Unspecified RESOLVED FIXED BlinkMergeCandidate P2 Normal --- 1 rniwa webkit-unassigned abarth aestes ap beidson oldest_to_newest 894778 0 rniwa 2013-05-29 01:44:14 -0700 We might want to merge https://chromium.googlesource.com/chromium/blink/+/cbf0eb3458947ff81a836599a692a9c1b32724c3 Now that detecting meta@charset doesn't block processing the resource, we need to be more careful about how we prioritize encodings from meta@charset relative to other mechanisms. Specifically, we meta@charset is supposed to be less important than autodetection from the "<?xml" preamble but more important than encodings detected from sniffing the content itself. 894966 1 ap 2013-05-29 08:36:45 -0700 We might take the regression test, but the code change is rushed, confusing, and it's just fixing a recent Blink regression anyway. 894969 2 ap 2013-05-29 08:37:02 -0700 Also, what's "NTP"? 915995 3 ap 2013-08-09 17:07:01 -0700 Landed the test in <http://trac.webkit.org/r153916>. 916021 4 abarth 2013-08-09 17:44:04 -0700 (In reply to comment #2) > Also, what's "NTP"? NTP = New Tab Page. It's the page you see in Chrome when you create a new tab. That's just where I noticed the problem, but the probably also occurred on other web sites. You shouldn't need the code change unless you want to try to detect meta@charset without buffering. If you do want to do that, there's another (even uglier) CL that you'd need to merge from later. 916037 5 ap 2013-08-09 22:30:56 -0700 Thanks Adam!