Make GTDInbox work with Firefox 3 RC1

This is how to get GTDInbox to work after you upgrade Firefox 3 beta 5 to RC1 on Windows XP.

1. Open Explorer, and go to:

"c:\Documents and Settings\YOUR_USER_NAME\Application Data\Mozilla\Firefox\Profiles\SOME_RANDOM_STRING.default\extensions\{bcd47b5a-43be-433f-9051-7ce2cdf94ac0}\"

The {bcd47b5a-43be-433f-9051-7ce2cdf94ac0} uniquely identifies the GTDInbox extension.

2. Backup your chrome.manifest file - copy it to chrome.manifest.bak

3. Open the chrome.manifest file in Notepad.

4. The very first line in the file should look like this:

content gtdinbox chrome/content/

5. Change it to:

content gtdinbox chrome/content/ contentaccessible=yes

and save the file.

6. You must now edit the install.rdf file in the same directory. First back it up, and then open it in Notepad.

7. You will see a section about 12 lines down that starts with < ! -- Firefox (spaces added to avoid HTML massacre by blogger.

8. On the line with element maxVersion, change the value (between the angle bracket tags) from 3.0b5 to 3.0 and save the file.

9. Sign out of Gmail if you are in there, exit Firefox, and open it again. You shouldn't need to clear your cache.

10. Open Tools->Addons and make sure GTDInbox is enabled.

11. Sign in to Gmail/Google Apps mail. If it worked, you will see the Compose Personal link, and your labels organised in the GTDInbox way.

Enjoy! ... and head over to http://productivefirefox.com/ and show your support for this clever AddOn.

[from info found here: http://forum.productivefirefox.com/index.php?topic=412.0]

Firefox CSS div / box model problem

The Problem: You've structured your page using a whole bunch of divs. Perhaps #top, #centre, #footer. Everything is inside #wrapper. Inside #centre you have several divs of class ".container". The containers comprise mainly of images - some of which are loaded from external sites. The containers are floated left so that their internal contents can also be floated. This is a standard scenario.

In firefox (1.5-2.0+), particularly if the images load slowly, there is an "overlap" effect, by which as the container divs fill up and expand themselves, the #footer, which has already been rendered, appears underneath the container divs.

In other words, the footer shows up first because it is just text and is rendered quickly. It will appear at the bottom of the page, say at 1000px down the page. The bug or feature in firefox means that as the divs above it expand they run down the page over the top of the footer which stays static in the place it was first loaded.

The Solution!
It is imperative that for every floated box/div, you also have specified a clear parameter. For things like content containers, or main page containers you can use clear: both. And for more complex layouts where you are mimicking tables, you can use clear: left or clear: right.

In my particular situation, I had not floated the #center div, and thus had also not specified a clear param. So, leaving #wrapper to take care of the centred positioning, I added the following lines to #centre:

float:left;
clear:both;

And for good measure, I added these to .container:

clear:both;


This seems to ensure that firefox will correctly push already rendered boxes down the page. Not sure if it's a bug or not. I guess it is, since in my understanding, divs have clear:both set by default, i.e. they are designed to act as paragraphs. I have seen other fixes such as the clearfix and the setting of height to 100%, but these didn't work for me. Perhaps they didn't apply.

Anyway, deep sigh of relief.