[Webkit-unassigned] [Bug 26694] should we scan beyond 1kB for meta charset?
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Wed Feb 8 20:49:29 PST 2012
https://bugs.webkit.org/show_bug.cgi?id=26694
--- Comment #12 from yosin at chromium.org 2012-02-08 20:49:29 PST ---
I ran mapreduce again to checking meta/charset position if HTTP response header doesn't have charset information.
<=1,024 95.71% 95.71%
<=2,048 2.97% 98.67%
<=3,072 0.67% 99.35%
<=4,096 0.25% 99.60%
<=5,120 0.10% 99.70%
<=6,144 0.06% 99.76%
<=7,168 0.04% 99.80%
<=8,192 0.02% 99.82%
<=9,216 0.02% 99.84%
<=10,240 0.02% 99.86%
How do we agree to use increased value(e.g. 2048, 3072) or use current value(1024)? Do we want to have another granularity (e.g. 100 byte) of coverage?
I vote to increase 3072.
--
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the webkit-unassigned
mailing list