I've gotten word that Gears will be updated to support Firefox 3.1 once Mozilla releases the first release candidate of 3.1. No sense in upgrading Gears while 3.1 is still in the beta phase since much can change between the beta builds and the first RC.
And yes, Gears is still being developed and is already up to version 0.5.8.0 in the development build of Google Chrome (the current stable release of Chrome has the same version of Gears as Firefox/IE uses: 0.5.4.2). I would suspect that version 0.5.8.* will be the version of Gears that Fireofx 3.1 will get once it reaches RC1. Hope this helps some. On 2/20/2009 10:53 AM, flubio123 wrote: > I think that Google Gears and Firefox 3 worked for me on Windows XP > SP3 but I was wondering if Google Gears will be supporting Firefox 3.1 > beta anytime in the near future. Thanks. > > PS - Has this project been abandoned? There have been no updates on > the blog since October so just wondering... > > On Feb 19, 5:42 pm, Will <[email protected]> wrote: > >> Mine honestly doesn't even get THAT far. Google gears did work for my >> friend in FF3. I don't know which update of FF3 he's using, though. >> >> On Feb 18, 10:35 am, Ken Han <[email protected]> wrote: >> >> >>> FF3 under OSX, XP and Server2003 is unstable for me as well, >>> especially when any settings are modified while Offline is enabled. >>> It simply crashes after saving a settings change. IE7 and 8 are fine >>> though. >>> >>> On Feb 17, 9:03 pm, Will <[email protected]> wrote: >>> >>>> I too would like to see a solution to this bug, if that's what it is. >>>> A bugfix would be even cooler ;D >>>> >>>> On Feb 9, 11:48 am, Ed V <[email protected]> wrote: >>>> >>>>> I am running Windows Vista Pro, I have IE8 Beta installed, and also >>>>> Chrome, and FF 3.0.6. Google Gears has been installed and I can access >>>>> offline my Doc's and Email from IE8 and Chrome. When I try it with FF >>>>> My browser locks up. I have uninstalled and reinstalled, no fix. I >>>>> have started FF in safe mode, I have disabled gears and re-enabled but >>>>> no fix. .... Help? >>>>>
