Talk about the native Mac OS X browser.
Moderator: Camino Developers
8 posts • Page 1 of 1
Version 2.1.2 (18.104.22.168 20120308211433)
Model Name: MacBook Pro
Model Identifier: MacBookPro4,1
Processor Name: Intel Core 2 Duo
Processor Speed: 2.5 GHz
Number Of Processors: 1
Total Number Of Cores: 2
L2 Cache: 6 MB
Memory: 6 GB
In recent months accessing the blogs I visit daily causes massive processor loads, swinging madly between one and another (Activity Monitor). Fans ramp up, the whole computer gets taken over, and is unusable until I close the blog page I'm trying to read. Dangerous Minds did this for a while; so did The Ael, now it's http://andrewsullivan.thedailybeast.com.
Anyone know what's going on and how I can fight it. Life with Camino is just getting worse and worse as it fades into the past.
There is a fix for this, if anyone cares- posted today in MacInTouch:
This works. ALL of the bad behavior I'd been experiencing in recent months has stopped. Thanks to all who chimed in here to offer assistance.
This is absolutely not the case, and claiming to be Firefox 13 will cause problems on other sites that require web content features available only in later versions of Gecko. (Also, no restart of Camino is required when changing the UA string, either by messing with that pref or by using the excellent UserAgent third-party prefPane. You will have to reload an already-loaded page so it sees the new UA string, but any new pages you load will see the new string immediately.)
I'm happy to see that it has worked for you and for the guy on MacInTouch However, be aware that it will cause problems on other sites, and if you run into problems, try reverting the change (or using a fresh profile) to see if the site works properly with the default user-agent string.
We debated eliminating the "like Firefox/foo" string entirely before shipping Camino 2.1, but the problem was that too many common sites were still sniffing for "Firefox" (instead of "Gecko" or "Gecko" and a Gecko version) and would serve Camino completely broken (or missing) content. Just dropping the version string (but keeping "like Firefox") didn't produce any significant change in the experience on the "broken" side or the "nagging for upgrade" side. We also weren't willing to change the UA string to blindly lie about browser compatibility by claiming to be some newer version of Firefox.
Unfortunately, the sad truth of the matter is that unless you are Chrome, Safari, Firefox, or IE, vast swaths of the web are still going to mis-handle you in one way or another. The situation has improved from 10+ years ago where only Netscape and IE were properly handled, but many web developers would still prefer there only be 1-2 standard browsers. And we need more manpower to get Camino to a more modern browser engine
Sorry to be late in replying myself. This is very interesting info, and much appreciated. Thanks!
I think this may be a 'your milage may vary' type solution.
I gave it a go, and right off the bat, it caused issues at PhotoBucket. (Mind you, I suspect PB causes a lot of their own issues ) That said, I think I'll just stay with 'spoofing' for the time being, and no . . . I'm not running on Intel, nor using 10.6.
8 posts • Page 1 of 1
Who is online
Users browsing this forum: No registered users and 1 guest