|Summary:||[Meta] Simplify the UA string|
|Product:||WebKit||Reporter:||Laszlo Gombos <laszlo.gombos>|
|Severity:||Normal||CC:||ap, fishd, laszlo.gombos, manyoso, phiw2, pkasting, tonikitoo|
|Version:||528+ (Nightly build)|
|Bug Depends on:||54560, 54566, 54567, 55226|
Description Laszlo Gombos 2011-02-16 08:02:46 PST
Following Gecko (http://hacks.mozilla.org/2010/09/final-user-agent-string-for-firefox-4/) and others WebKit should consider simplifying the UA string in concord with other WebKit based ports/browsers/products.
Comment 1 Alexey Proskuryakov 2011-02-16 14:09:47 PST
An obvious concern with changes like this is that sites will certainly break. Scripts that check navigator.userAgent do that in most weird ways. For example, there used to be sites that broke if "4." was found _anywhere_ in the string, because they assumed running under Netscape 4 then (or IE 4? I don't remember all details).
Comment 2 Peter Kasting 2011-02-16 14:17:48 PST
I'm sure there will be some bustage. Hopefully the mitigating factors are: * Chromium has the ability to push changes to smaller populations and get real-world feedback quickly, so it would be useful for us to test this first * If we make the same changes as Gecko and at the same time, site authors are more likely to see bustage and have more incentive to fix it correctly We've tested UA string simplifications before so we may have some QA experience or tools from the last time we tried. Darin Fisher might know more.
Comment 3 Peter Kasting 2011-03-09 22:37:28 PST
At this point all the UA string changes I intend to make have landed. I'm going on vacation tomorrow, but I've sent draft blog posts to some of the Chromium folks that can post on both Chromium and WebKit blogs, in order to provide some clear, public documentation of what's changed. There's been some bustage on Google sites, but we fixed the problems in Google's UA parsing libraries and at least some sites have pushed out updates to fix things. Beyond that, I haven't heard much fallout so far.