Is there still a 3.7a2pre that should be called something else and reinstalled from
somewhere else for testing. Surely 3.7 and 4.0 are not the same.
Extension compatibility in betas now has to be done through an extension,
Add-on Compatibility Reporter :: Add-ons for Firefox
https://addons.mozilla.org/firefox/addon/15003/
Had used it before, but now it appears to be mandatory.
> I had installed Firefox 4.0b1 and was testing, then today, my
> Minefield 3.7a2pre got updated to Minefield 4.0b2pre and the
> Firefox 4.0b1 remains behind.
>
> Is there still a 3.7a2pre that should be called something else and
> reinstalled from somewhere else for testing. Surely 3.7 and 4.0
> are not the same.
There's no more 3.7. Separating plugins from the main process was its
major focus, and that work got ported to 3.6.x. Other stuff that was
going into 3.7 may show up in further 3.6.x releases, but much of it
will be part of the 4.0 release.
--
»Q« /"\
ASCII Ribbon Campaign \ /
against html e-mail X
<http://www.asciiribbon.org/> / \
Okay thanks and Minefield remains Minefield other than wasted time
on 4.0b1 everything good as far as versions is concerned, can't find
anything good to say about the change to the user interface -- oh
can move buttons into bookmarks toolbar and to the tabs bar that
could be good for those that don't have them filled up and it makes
sense for them to do it.
had space there.
the same about the changes to the user interface.
"custom.firefox.lady" wrote ...
> "David McRitchie" wrote...
>> Extension compatibility in betas now has to be done through an extension,
>> Add-on Compatibility Reporter :: Add-ons for Firefox
>> https://addons.mozilla.org/firefox/addon/15003/
>> Had used it before, but now it appears to be mandatory.
> Not really. You can just use:
> extensions.checkCompatibility.4.0b set to false.
Thanks for the heads up.
Pretty sure I had that all along, deactivated the extension installed a
new extension and it installed. Don't know what happened before,
most extensions were disabled and could only reinstall them, enable
was not a choice. Was caught by surprise when Minefield 3.7a4pre
turned into Minefield 4.0b2pre after having tested separately with 4.0b1.
This was probably the best transition of Minefield so far between versions,
since I didn't have to reinstall, rename or redo profiles for Minefield.