Mozilla Firefox 1.5 released

Version 1.5 of Mozilla Corporation’s Firefox web browser has been released with a whole bunch of improvements and bug fixes. For instance, the annoying rounding error that would sometimes cause a horizontal line to be displayed in boxes created with my Transparent custom corners and borders technique and the bug that prevented Alex Robinson’s Any Order Columns technique from working have both been fixed. Great! Now I’m just waiting for all the extensions I use to be updated to work with Firefox 1.5.

Firefox 1.5 is available for download at the new Mozilla Corporation website.

Update: If you regularly use any extensions that aren’t compatible with Firefox 1.5, try following the instructions given by Stuart Colville in Firefox 1.5 Launched. If you’re lucky you can make your favourite extensions work with 1.5. I tried fixing Checky, but I get an “Install script not found” error when I try to install itand it works fine when I recompress only the files inside the folder, not including the folder itself.

Posted on November 30, 2005 in Browsers, Quicklinks

Comments

  1. I have to get used to saying “Mozilla Corporation”. ;)

    All my extensions passed the check, what are you using?

  2. Roger, have you seen that the Validation plugin has been updated and is now 1.5 compatible? Don’t know if you use it, but it can be a “quick and dirty” way of spotting errors fast.

    See you tomorrow, btw! :)

  3. Gah. We go to Mozilla.com, and what do we see?

    • A big heading saying “Firefox 1.5
  4. I love how half my extensions break with every update to Firefox. Really makes me feel like I’m using an open-source product.

  5. Whoops. Let me start again:

    • A big heading saying “Firefox 1.5”
    • A nice big download link, with very small text revealing that it’s for Firefox 1.07
    • Another nice big download link, identical except that the small text tells us that this one is Firefox 1.5

    Why on earth have they put a link to the older version above the link to 1.5, on the day they release 1.5 in a blaze of publicity?

    I mean… why?

    Best of luck attracting switchers with this kind of confusion.

  6. Sorry, my bad: they just haven’t finished the English (British) version of 1.5 yet.

  7. Could always download the RC3 English (British) version and wait patiently for the “new” updater to kick in :)

    PS. Can someone find RC3 (British) anymore? hmmm.. so much confusion, they should just post the RC3 British version instead of 1.0.7!

  8. November 30, 2005 by Roger Johansson (Author comment)

    Mats: The HTML Validator plugin, but I see from Anton’s comment that it has in fact been updated. Goodie :-).

    See you tomorrow, btw! :)

    Yep!

  9. November 30, 2005 by Roger Johansson (Author comment)

    Hmm. Just noticed a couple more extensions that aren’t compatible with 1.5: Fangs and Checky.

  10. I’m liking the update, its much faster in rendering pages and faster at going backwards/forwards. The nice wee features added are good but I’m pleased to see they haven’t changed FF to much, and security updatea are always useful heh. The only extionsions not to work in 1.5 for me are crappy ones I don’t use.

    I’ll be interested to see how the website reporting tool works. What exactly happens after you report a site doesn’t look right? hmmm.

    Small Paul whats with all the complaining? o_0 Were you jumping ahead of yourself because the download page looks perfectly fine to me.

  11. Yea I saw that Fangs, Web Color Names, Live HTTP Headers and CuteMenus was broken too.

    And that DOM inspector 1.0 was replaced for DOM Inspector 1.8 instead of updated for some strange reason.

    Wanna see something really cool though, click “Find updates” in the Extension window … rockin

  12. November 30, 2005 by Rob E.

    Been using FF 1.5 since RC2 and it has been great. The new update feature is a huge improvement to previous version.

    The only plugin that doesn’t work is the Adblock extension. Somehow I can’t get it to work. Apart from that all other installed extensions seems to work though.

    //Rob

  13. You can get a fixed version of fangs and a couple of other extensions here.

    I’ve also listed some basic instructions for amending the maxVersion which is often the reason why the extensions don’t work.

  14. But what about the huge amount of people that won’t switch to the new Firefox? How are you supposed to test for an older version without using something like SiteVista?

  15. November 30, 2005 by Roger Johansson (Author comment)

    Stuart: Ah, thanks!

    Edward: Firefox is not Internet Explorer, so there is nothing stopping you from having multiple versions installed. Just keep the old version for testing :-).

  16. Oh my, I never even considered that. Being around IE so much has just caused me to have that misconception. Many thanks!

  17. Refering to your update: You get the “Install script not found” error when you pack the whole folder in a zip. Try packing just the files inside the folder. This way it worked for me with checky.

  18. November 30, 2005 by Roger Johansson (Author comment)

    joern: That did the trick. Thanks!

  19. Paul Haine wrote:

    I love how half my extensions break with every update to Firefox. Really makes me feel like I’m using an open-source product.

    Seriously? It’s the responsiblity of the extension developers to update their extensions. You can’t expect the internals of the browser to stay the same when you move to a new version…

  20. And as for getting older extensions to work, there is also an about:config hack which should be easier than the hack mentioned in the post, as you don’t have to hack each extension you want to install.

    How to make older extensions work in Firefox 1.5 beta.

  21. I heard about some memory problems with FF1.5, It can take over 400MB, for now I haven’t got that problem, but we will see.

    Marcin

  22. One thing that annoys me is that apparently, the “dotted borders” around active (clicked) links are now drawn outside the link as opposed to Firefox 1, where they’ve been drawn inside the element (at least it looks that way with my installation). That’s fine in text, but if you’ve got links with no margin to the sides of the viewport or something like that… yout get fancy horizontal scrollbars when you click them.

    Does anyone notice this, too? And know if that change is intentionally? Correct behaviour? A bug?

    PS: Fixed it by making the links 1px shorter, so you can’t see it on my site.

  23. I managed to luck out on all of the extensions that I use. I was really upset when I first ran 1.5 and it told me that it was disabling several of my extensions. But then I went out and looked for updates, and I discovered that each of the extensions already had either a 1.5 beta version or a 1.5 specific version released. Now my extensions are back, and my browser is better. Nice work from the community on this one.

  24. Marcin Andrzejewski: I’m sure that was firefox 1.0, it would not unload tabs from the memory once they were closed so the more tabs you opened the more memory it used. This doesn’t seem to be a problem with 1.5. I may be mistaken though.

  25. Hmm, Add Engines seems to be completely screwed and doesn’t work at all in mine, you add 3 in a row, the first one disappears and it puts them in random places around the bottom of the list!?!? Anyone else experience that?

  26. December 1, 2005 by Elliot Winkler

    If you want to force your extensions to work with 1.5 (assuming they worked in 1.4), use the Nightly Tester Tools. You can even force extensions as you’re installing them, which I like.

  27. I’m able to make Fx 1.5 Mac unusable by simply having an alert() function inside an onmouseover event - do it to a few items on a page (like building a menu navigation system) and the OK button in the dialog “sheet” isn’t clickable. What’s more, keep hovering over different elements with the onmouseover behaviour ends up with a huge string of blank entries in the Window menu. And of course, nothing (including any items in the application’s menu bar) is clickable. Anyone else find this?

    Fx 1.5 Mac still feels like a beta to me…

  28. December 13, 2005 by Anthony

    Hi Alex,

    I have found a very similar problem on 1.5 for PC. An alert on an INPUT tag’s onMouseOver event causes a loop IF the alert box (it may even be just the OK button of the alert box) covers the INPUT box that triggered it.

    The quicker you clear all the alerts, the fewer are generated. While it is looping the focus switches between alert and main page.

  29. December 13, 2005 by Anthony

    P.S. I haven’t been able to find a Bugzilla bug number but the problem I described seems to be fixed in the Deer Park Alpha 2 build for 2005-12-12.

  30. D’oh! Thanks for pointing out that compressing the folder is a bad thing.

  31. I just recently upgraded to firefox 1.5 and lost all of the engines that I had enstalled. firefox won’t allow me to add engines- everytime I try to add an engine is send me to “The connection was interupted page”. Additionally, I lost two of my extensions that I had- they are no longer compatable with 1.5. Does anyone have any ideas on how to fix this?

  32. Any chance of posting the .xpi for Checky? I still haven’t been able to get it to work in FireFox 1.5.

    I miss the ability to check a web page against the W3C’s html/css validators and run the full gamut of accessibility tools with a single keystroke. Checky is such a simple interface. What a time saver it was.

    Thanks.

  33. February 25, 2006 by d.rich

    After upgrading to firefox 1.5, firefox just lost all the engines I had installed. It doesnt allow me 2add any.

    It no longer responds when I click “search for…” under thh right-click menue.

    but most importantly..it Lost All my bookmarks.. I realy cant beleive that even now…! how can this be solved.

  34. March 6, 2006 by Gawen Crow

    I’m having the add engines problems as well, lost all my engines with the upgrade and can’t add new ones. Whats the fix for this? To me thats the most important feature of the browser.

Comments are disabled for this post (read why), but if you have spotted an error or have additional info that you think should be in this post, feel free to contact me.