Zorra Veloz, a Firefox 2 Based Browser

On account of being dissatisfied with OS X browsers, I decided to hack out my own compilation of Firefox 2.0.0.3 for my Intel based MacBook Pro (what I call my MacTel). After spending the better of a day reading seemingly about 20 Mozilla pages, seriously, I got some working builds.

I was surprised to see that a few nagging problems that the official Mozilla builds have disappeared.

“* a crash that occurs when (de)selecting the Preferences javascript checklist, and
* the lack of refreshing after deletion of a Bookmark from within the Bookmark Manager.
* The browser seems more responsive, feels more like a native OS X application and less a port.”

I also optimized the builds via various settings and refused to build any crud (no offence) that might slow things down such as,
-ldap
-canvas
-svg

I was surprised to see that sites like Mozilla related projects (such as Epiphany on some points) recommend disabling the following options as Firefox shouldn’t contain support for them due to the fact that it is not a suite anymore.
-newsreader
-chatzilla
-composer
-calendar

Among the apparent .mozconfig misconceptions I find for mac builds are,
ac_add_options –enable-static
ac_add_options –enable-static-libs

The second should not be necessary because the first eliminates dynamic building. Furthermore, I can’t find any documentation to support the “–enable-static-libs” option either at the Unix Build Configurator or at the User:Biesi/Configure options.

These too seem to be erroneously configured leading to bloat,
ac_add_options –without-system-nspr
ac_add_options –without-system-zlib
ac_add_options –without-system-jpeg
ac_add_options –without-system-png
ac_add_options –without-system-mng
ac_add_options –enable-crypto

My own testing suggests that these are not necessary, as my builds work well without the above options. Looking into the matter I found this,
“If you are building binaries that will be distributed to a wide variety of systems,
or which do not have all the same shared libraries to link against at runtime,
building mozilla’s zlib and jpeg libraries for distribution is a good idea.”
http://www.mozilla.org/build/distribution.html

OS X platforms should be similar enough as to not necessitate compensation for a wide tolerance in non-conforming placing of dependencies.

Lastly, “–enable-crypto” should not be necessary as Configurator allows disabling it, suggesting that the default is enable, but this may be because of these Gnu/linux based apps use older Mozilla Firefox code (1 series) when the defaults were different.

Google doesn’t seem to be a great tool in as far as finding info for your Mozilla developer needs, and I found irc Firefox, Seneca, and the main developer’s site non-responsive. But this may be due to a lack of developer knowledge in the ff room and there being few developers in the developer irc. If you’re looking for assistance, the best solution seems to join a mailing list.

Anyway, feel free to try my MacTel builds located at here. Don’t ask about the name of the site.

Maurice Cepeda

Update: Okay, I think I know why it is beneficial to use,

ac_add_options –without-system-nspr
ac_add_options –without-system-zlib
ac_add_options –without-system-jpeg
ac_add_options –without-system-png
ac_add_options –without-system-mng

Seems that not building in this support disables me from seeing images remotely (show up as “broken”) but upon selecting them I can see them. ie., Google’s image search brings up broken images but selecting them allows images normally.

Then again not maybe not because Firefox 2.0.0.3 shows the same problem. Seems the problem is with Google. Will update.

Update on update: The problem is with the Firefox 2.0.0.3 code because the “Load images automatically” option in Preferences was selected properly. De-selecting it and refreshing the Google image results page, then reselecting the preference selection and again refreshing the same page suddenly makes the images magically appear. Images now work in Zorra Veloz too.

Somebody has to clean up this Firefox 2.0.0.3 code because even doing your own builds doesn’t take care of all the bugs.

This is licensed under the Attribution-NonCommercial-ShareAlike 3.0 Unported Creative Commons License. All brands mentioned are properties of their respective owners. By reading this article, the reader forgoes any accountability of the writer. The reading of this article implies acceptance of the above stipulations. The author requires attribution –by full name and URL– and notification of republications.

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s