You are currently browsing the tag archive for the ‘firefox’ tag.
A good alternative browser to Safari on Mac OS X Leopard is Camino. Camino is based on Mozilla’s Gecko engine, so it operates much like Firefox on Mac, but a hell of a lot quicker.
Camino just released version 1.6.1 (May 20, 2008), which fixed stability and security issues from their last major release, 1.6, which was made available a month before that, so the latest release should be pretty solid.
Having offered Camino as an alternative to Safari, I actually not only still use Safari, but I also use Firefox, basically the three major browsers on Mac. Why the heck would I do this? Each browser has its benefits.
Best overall website compatibility. Lets face it, Apple still has a ways to go before Mac penetration gets beyond even 15% of the user base that Windows has. As such, most websites are optimized or tested for “Internet Explorer” and none other. This can lead to rendering issues on Mac browsers such as Safari and Camino. Firefox is the least susceptible to these compatibility issues, which are generally due to Internet Explorer not being standards compliant. But, that’s another story for another time, by another blogger.
Fastest browser. Faster than both Camino and Firefox. Safari is what I think of as a “light browser”: a lean, mean, browsing machine. This was the first browser for Mac and it’s the most “integrated” with the operating system. But, it lacks some “power-user” features that I can’t live without on a day to day basis. For example: text or link searching using “forward slash” or “single quote”. In Camino simply hit the “forward slash” key, start typing, and Camino will move to the next word containing the string of characters you are typing. Hitting Ctrl + G will move to the next match. The same works with “single quote” link searching. Once the link you’re searching for is found and highlighted, simply press Enter/Return and the link is opened. This is seriously efficient and fast browsing, much much faster than messing around with a mouse or trackpad and hovering the mouse pointer over the correct few centimeters of display in order to open links. Try this inline search feature on Camino and I bet you will love it.
Safari has its own search/find feature that’s pretty tight as well, highlighting the word you’re searching for and darkening the rest of the page. This is great for serious text reading on big documents, but for navigating and general surfing, I’d much rather have Camino’s inline search with keyboard navigation.
Error: uncaught exception: Permission denied to call method XMLHttpRequest.open FireFox/Mozilla browser fix / solution:
- Go to address “about:config” in Firefox (i.e. type that in the address bar and hit Enter)
- Search for “signed” in the filter bar
- Double click the item “signed.applets.codebase_principal_support” to change its value to “true”
- Create (or edit if already present) the “user.js” file found in the below directories. By default this file does not exist so create a new blank user.js file if you don’t find it in the following paths (as specified on Mozilla.org):
- On Windows Vista/XP/2000, the path is usually
%AppData%\Mozilla\Firefox\Profiles\xxxxxxxx.default\, where xxxxxxxx is a random string of 8 characters. Just browse to
C:\Documents and Settings\[User Name]\Application Data\Mozilla\Firefox\Profiles\on Windows XP/2000 or
C:\users\[User Name]\AppData\Roaming\Mozilla\Firefox\Profiles\on Windows Vista, and the rest should be obvious.
- On Windows 95/98/Me, the path is usually
- On Linux, the path is usually
- On Mac OS X, the path is usually
- On Windows Vista/XP/2000, the path is usually
- Place the following lines within user.js:
- Edit the line containing “http://localhost.com:3000″ and replace that URI with whatever URI you are developing on (or publishing to). For me it happens to be localhost.com:3000. Normally it would be just “localhost” for most people or localhost:3000 for Rails project developers.
- Save the user.js file
- Exit out of Firefox or other Mozilla based browser. If on Mac OS X, fully quit Firefox by hitting Cmd+Q, don’t just close the current browser window (which leaves Firefox still running in the background).
- Launch FireFox again.
- Exit out of Firefox again. The config file that Firefox actually uses to control the browser is called “prefs.js”, not “user.js”. user.js is the file that we, the end user, are supposed to make changes to, which are then copied over to prefs.js when Firefox is loaded. For whatever reason, the prefs.js file will not be updated with the contents of user.js until you exit Firefox, launch it, exit again (at which point prefs.js will be updated), then launch Firefox once more and your changes are ready for use.
After the above steps are completed, you should be able to make XMLHttpRequest calls cross-site / cross-domain with your AJAX code without Firefox/Mozilla security getting in the way.
The bevy of user_pref settings above creates a new site security policy that allows the listed XML HTTP Request commands to be performed from “http://localhost.com:3000″ to any address. Normally, Firefox will only allow XMLHTTP Request calls within the same domain. For example if you were on microserf.com domain, Firefox would not allow the website http://www.microserf.com to make XMLHTTPRequest calls to http://www.hackmehard.com since this was a major exploit that crackers would use to hide their evildoings in the background of apparently benign sites.
In general the security policy that Firefox has setup by default is a good idea. Setting up a new security policy as we have done above is generally safe as it only allows the site “http://localhost.com:3000″ to make cross-site/cross-domain XMLHTTPRequest calls of any sort listed. Any other domain would not be allowed to use this site policy.
So something that came as a bit of a surprise to me was that on certain sites, Safari is 4-5x faster than Firefox on page rendering. Recently I’ve been doing lots of work on SalesForce.com and I was thinking: “Man, their site is hella slow”.
After talking with a friend in Paris accessing the same site, but without all the slow loading issues I decided to give Safari on Leopard a try. The exact same pages, the exact same actions produced very different results. Safari is by far the “fast browser” and Firefox, the slow browser, at least on OS X. Pages that I would have to wait between 6-7 seconds to finish loading in Firefox would come up around the 1 second mark (or less) in Safari. This is an enormous difference when you’re talking about browsing as 5-10 seconds is an eternity to wait for something to load, but too short of a time to do anything meaningful besides becoming frustrated.
Now if only Safari could navigate links using the keyboard only like it’s possible in Firefox. In Firefox you can simply Ctrl + F to do a word search on the page (which is part of a link), when the partial word/link is highlighted, hit Esc to clear the search highlighting and you’re left with a cursor focused link that will respond to an Enter button press with opening the link. Brilliantly fast, much faster than finding links through the mouse. Somehow we need to generate enough noise so that the Webkit (which is the basis of Safari) developers to take note and build this into the next release of their software.