Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

Click here to return to the 'The main problem isn't really giving credit' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
The main problem isn't really giving credit
Authored by: vykor on Jul 06, '09 01:19:15PM

The main problem for the user isn't really giving Safari credit, so much as that many websites detect your browser via the user agent and deploy custom CSS or JavaScript. This is usually used to work around edge cases & bugs in site rendering or script execution -- especially for Javascript-intensive, AJAX-y sites.

If your user agent doesn't conform to the "Mozilla/xx ... Safari ... WebKit" style string exactly, the web app may fail to detect your browser correctly. You may get served the wrong thing, which makes the site render badly (CSS for Mozilla browsers that don't get the -webkit-* attributes for example, or even an IE stylesheet), break certain script functions, or skip browser-specific optimizations.

The moral of the story: it's in your best interest to use this appropriately, not to change your browser to report "Vykor's Awesome Intarweb Engine/1.0".

[ Reply to This | # ]
The main problem isn't really giving credit
Authored by: Felix on Jul 07, '09 04:27:23AM

I don't disagree with anything you've written! As I said before...leave it on the default setting (which will also help the various web site owners get a feel for the volume of Safari traffic) UNLESS Safari won't properly render/display a site. Then try changing the UA while you're on the site.

Of the sites I frequent on a regular basis, few require the workaround anymore.

[ Reply to This | # ]