This was done for compatibility. Unfortunately a lot of web sites look for "safari" in the UA string to determine if they should tailor their content for webkit! It is a very sad state of affairs. All webkit based browsers (e.g., Omniweb) include "safari" in their UA strings for this exact reason, I suspect. That said, we wish we didn't have "safari" in our UA string, and we are going to be studying the effects of removing it in an upcoming dev channel build.
-Darin On Thu, Sep 25, 2008 at 12:02 AM, HLS <[EMAIL PROTECTED]> wrote: > > Is there a reason why the User-Agent: header for chrome includes both > itself and Safari? > > Like so: > > User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US) > AppleWebKit/525.19 (KHTML, like Gecko) Chrome/0.2.153.0 Safari/525.19 > > I'm sure you guys had a reason for this. > > Maximum Compatibility because systems may not be looking for "Chrome" > tags yet? > > Our server side scripts are picking it up as a "Safari" browser which > I guess, right now, it is a good thing to work with template. > > I guess at some people the safari tag will be removed? > > --- > > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/chromium-dev?hl=en -~----------~----~----~----~------~----~------~--~---
