The Journey to Update Firefox from 1.0.7 to 1.5

Just a few weeks ago, Mozilla released Fire­fox 1.5 RC3. This seems to be the same as the final release. So, if you haven’t con­verted yet (mostly IE6 users) nor have tried out Fire­fox, now is the time.

Mozilla Firefox

I finally decided to update my Fire­fox ver­sion from 1.0.7 to the newest 1.5. I will be imple­ment­ing this on my work PC as it has the most exten­sions installed. This should be interesting.

Here are the extensions:

  • Web Devel­oper 0.9.4
  • Wizz RSS Reader 1.1.0
  • gTrans­late 0.2.6 gTrans­late 0.2.7
  • ShowIP 0.7.11
  • Col­orZilla 0.8.2 (New ver­sion: 0.8.3)
  • Grease­mon­key 0.5.3 Grease­mon­key 0.6.2
  • fireFTP 0.88.3
  • Site­bar Side­bar 1.02
  • Tab­browser Exten­sions 1.14.2005092501 (New ver­sion: 2.0.2005113001)
  • View Ren­dered Source Chart 1.2.03
  • Screen­Grab 0.6
  • HTML Val­ida­tor 0.7.6
  • Aut­ofill 0.2
  • IE Tab 1.0.5 (New ver­sion: 1.0.6.4)

Here goes noth­ing, or some­thing. To be con­tin­ued

Updates
The striked-out exten­sions above were noted as incom­pat­i­ble with Fire­fox 1.5. Fire­fox Update auto­mat­i­cally “dis­abled [them] until com­pat­i­ble ver­sions are installed.” I then noted the newest, avail­able ver­sion of the exten­sion that is com­pat­i­ble with Fire­fox 1.5, as stated by Fire­fox Update.

Also to note, I needed to update my theme “Noia 2.0 (extreme)” as it was caus­ing a dis­play bug on the URL-address bar. This went from 2.88 to 2.991 and appar­ently fixed the dis­play issue. This took a while to fig­ure out. Maybe in the future, Moz-dev team can have a note to check one’s theme if there are any dis­play issues being encountered.

All in all, the update went quite well. It seems that Fire­fox 1.5 loads a tad faster than its pre­de­ces­sor. I’m just bummed about not hav­ing some exten­sions: Site­bar Side­bar (which is my links depos­i­tory) and Grease­mon­key (which is one of the best exten­sions to have for a Fire­fox user).

Note: Grease­mon­key 0.6.2 seems to be hav­ing bug issues at the moment. Peo­ple have been address­ing this issue, so there should be a fix soon. It’s prob­a­bly going to roll out with ver­sion 0.6.4 of the extension.

2 Comments

Comments Feed