I updated to Shiretoko (Firefox 3.5 developmental) version3.5 pre last night. This marks the en dof the Beta builds for Firefox 3.5 and means there should be an upcoming Release Candidate soon. Everything for the most part went as expected with this update including about 1/3 of my add-ons becoming disabled. The add-ons all appear to be working fine now once they were force installed via the Nightly Tester Tools.

However, when I went to compose a blog post in Firefox 3.5, I could not get the ‘Visual’ editor to work correctly. No, it did not crash my browser like it did earlier this year with the AdBlock Plus conflicts. It simply does not work. So I switched over to my Firefox 3 (3.0.8) build and seems to be working fine. I thought it may have been an extension but I am running the same set of add-ons in both the Firefox 3.0 and 3.5 builds. With a couple minor exceptions, I have one extension in 3.0 that I don’t have in 3.5. Further it appears NoScripts and Personas need to be updated along with Firefox 3 itself.

So, after this post I amgoing to restart thus upgrading to Firefox 3.0.10 and to the latest versions of NoScripts and Personas. I’ll see if I can duplicate the oddities I having with WordPress, this will determine if it is an add-on or the new 3.5 build that is conflicting.

Update: After updating from Firefox 3.0.8 to 3.0.10 along with updating both Personas and NoScripts, WordPress still works fine in Firefox 3.0 and doesn’t in Firefox 3.5. Just for good measure I also removed the extension from my 3.0.10 profile that I was not using in 3.5, just in case for some really odd reason it was causing WordPress to function correctly.

Update 2: Here is my current add-ons via Infolister: