Mozilla's Firebird Web Browser Released For Mac
Firefox for mobile, codenamed Fennec, is a web browser for smaller non-PC devices, mobile phones and PDAs.It was released for the Nokia Maemo operating system (specifically the Nokia N900 and N810) on January 28, 2010, [50] and is in development for Windows Mobile and Android. [51]Firefox for mobile 1.0 uses the same version of the Gecko layout engine as Firefox 3.6.
I Just tried 0.7.1 and it is definitely faster for the sites I go to. It's especially faster for SSL sites (that's a big Safari complaint I have - SSL is s.l.o.w; Ive whined about it before on /.). I use Firebird/Mozilla on WinXP/2K/2K3, Linux, BSD and Solaris and would love to see Camino base itself off of the Firebird fork and make it more Mac-like, but, until Safari get's an SLL clue, I'll take the fast rendering, good SSL performance and standards' compliance that seem to be there with 0.7.1. One other thing it has over Safari is the ability to.not. wait for the whole stupid page to load before continuing.
It's not a problem on all sites, but it happens more oft than not, again, especially on SSL sites. Lastly, the best thing about it is that it doesn't use the brushed metal theme (it was nice for a while, but it really grates on ya over time). I still don't know why Apple threw the KHTML folks the bone when they should have supported Mozilla. One other thing it has over Safari is the ability to.not. wait for the whole stupid page to load before continuing. This is a diffy one, and I think Camino does it too, and it really irks me to no end and has done for some time with all browsers. I think the key is learning how to ignore threads you already have out there.
You can't kill them, so you have to ignore them. There's a performance trade-off, but it need not be so bad. I've done something similar with a network utility and it seems to work OK.
Safari (like Internet Explorer on Windows boxes) will have the benefit of tighter OS integration. The tabs are also better in Safari, but it wouldn't take much for the Mozilla folks to 'get it right' (grin). There is (at present) no nice way to do font stuff in Firebird.
Mozilla Firebird Browser
That will catch up before 1.0. No SnapBack support in Firebird either. Safari 'feels' like a polished, professional application; Firebird still has a bit to go, but it will get there, especially if they take the fork for Camino suggestion i. The one thing I really, really like about Firebird on the Mac is the single button to make all the toolbars disappear. I have an older iMac with a small (1024x768) screen.
Often, after navigating to a web site, I want to switch to some approximation of 'full screen' mode. In Safari, that is four steps: the three keyboard combinations to make the status line, bookmarks bar and navigation bar disappear and then click the 'zoom' button to re-expand the window to full screen. (Why does the window shrink when. I mean, you are right that the theme makes Firebird (and Mozilla, for a while now) look like aqua, but it's not actually using real OS X widgets. Get a copy of Moz or Firebird for Windows and you can do the Pinstripe theme as well; it doesn't rely on carbon or cocoa for ui elements.
Good, I say, that the Pinstripe theme helps the browser fit in better- it's just not the same, exactly, as other OS X apps. Even though I'm nitpicking here, it's kind of useful and interesting info. That's correct. If you work around the site's OS check and install the theme on windows you'll get the Aquafied icons but not the actual pin stripes, UI controls (buttons, scrollbars etc).
They'll look like Windows controls to an extent since the Windows implementation of the theme renderer is doing the drawing. FWIW - many apps on MacOS use highly customized widget sets that are not part of the collection of 'stock' widgets provided by the OS, including Adobe Photoshop, Macromedia Dreamweaver, Internet Explorer and even Safari. These 'owner draw' widgets are effectively the same concept as Firebird with its native theme renderer + XUL. The deal with Firebird is that because it's in its pre-1.0 state on MacOS X not all of the rendering glitches have been corrected.
I used to use Camino as my primary browser until shortly after Safari 1.0 came out, but I have also been keeping my eye on Firebird simply for its cross-platform capabilities. In my experience, there is very little difference in any of the browsers out there for Mac OS X, aside from various UI and preferences differences. But specifically for Firebird versus Camino, I think the only thing that Camino has over Firebird is the snazzier Aqua UI. Firebird is still butt-ugly - not that that's a bad thing in the grand scheme of things, because I'm just a vain Mac user. (I do of course pity those who don't realize that you CAN choose 'pretty' - or to put it nicely, 'aesthetically pleasing' - appearances for my apps. But since I'm on the Apple part of /.
Here, I'm probably preaching to the choir now.). As a Mac user, there are four major browsers from which I can choose.
Each has their little quirks that annoy me. For example:. Camino: no way through the GUI to disable image animation; relatively little information about cookies if you ask for cookie prompts.
IE: bloody ancient. Poor cookie control. No way to disable image animation.
Safari: no way to disable image animation. Poor cookie control.
Jun 19, 2013 - Select the file or folder in the OS X Finder, then hit Command+i to summon Get Info. Click and drag alongside “Where” to select the path, then hit Command+C to copy the full path to the clipboard.
Mozilla Firebird Web Browser Released For Mac
Metal interface (although that's fairly easy to fix). Mozilla/Firebird: Proxies aren't linked to the Mac OS network preferences.
(You'd be amazed at how annoying that is when you're shuffling a laptop between work and home.) Non-native widgets (minor irk from my point of view). If somebody could change Firebird to link proxies to the network preferences, it'd be ideal - I'd live with the non-native widgets quite happily. Or a cookie manager for Safari.
Mozilla/Firebird: Proxies aren't linked to the Mac OS network preferences. (You'd be amazed at how annoying that is when you're shuffling a laptop between work and home.) It's doubly annoying since there's an obscure bug with squid transparent proxy/cacheing not working.
With my squid server at work, it works fine. With the squid configuration that my ISP has, it's broken and I get nothing but timeouts. It works great with every other browser, though.:-( http://bugzilla.mozilla.org/showbug.cgi?id=.