Will this resolve memory leak trouble that some (or many) have?
tedster
10:25 pm on Aug 29, 2012 (gmt 0)
This new version sure isn't currently compatible with a pile of add-ons that I use regularly. Looks like a lot of the technical burden was pushed to the add-on creators.
g1smd
10:50 pm on Aug 29, 2012 (gmt 0)
I'm over this 'change the major version number every three months' nonsense.
lucy24
11:11 pm on Aug 29, 2012 (gmt 0)
... leading to generic advice for all UA version-based blocking everywhere:
Make sure any Regular Expression anywhere in the form [1-somenumber] comes with a following \. or / or whatever is appropriate. Otherwise you'll be locking out humans using version 32 when you only meant to exclude robots wearing version 3 ;)
:: off to double-check htaccess, which has already been fine-tuned for MSIE 1-4 ::
feiling152
7:55 am on Sep 19, 2012 (gmt 0)
Fireox 15 is out but its toolbar and others tools is not available now.
Robert Charlton
8:57 pm on Sep 27, 2012 (gmt 0)
I'm over this 'change the major version number every three months' nonsense.
Yeah... I'm on "the release update channel", and I'm wondering whether the other channel (I forget what they're calling it) might be preferable. I'd hate to miss security updates, with each update I need to consider whether I might obsolete a bunch of tools I depend on. So I try never to update any critical app when I'm right in the middle of a project with an important deadline.
I've just finished up on a big one and noticed that the new Google Trends isn't displaying in FF v13.0.1 (for whatever reasons), but it looks like now's not the time to see if an update would fix it.
