Firefox updated

[meo]

Hi!

Just a quick note that Firefox has bumped to 3.5.1 it seems.

Have fun,
meo

[meo]

Hi!

Sorry Jason, I should have checked if the Firefox extension already was updated before posting a reminder. A stupid mistake I did so just forget I ever mentioned it.

Have fun with the valuable work you are doing,
meo

[junan]

now firefox 3.5.2 , can not wait for the tce/z

[Jason W]

Meo - no problem.

They must have updated Firefox last night as I swore I checked on it yesterday.  I will make Firefox/Shiretoko 3.5.2 tonight if nothing gets in the way.

[Jason W]

Firefox/Shiretoko will get updated to 3.5.3 tonight if circumstances permit.

[Jason W]

I see 3.5.4 is out.  Will update Firefox/Shiretoko tonight.

[JoXo009]

This morning an automated firefox update happened to me I thought would be impossible.



What does that mean? - Is such updating safe in TC?

[JoXo009]

Or maybe it was no autoupdate?

Just see in appbrowser:
firefox.tcz
Firefox web browser
Version 3.5.3
...
last line:
2009/10/29 Bumped to 3.5.4


So maybe its only a misleading title of the extension?

[Jason W]

Some folks want the official Firefox, which I have no control over the features that is was compiled with (autoupdate, urlclassifier, etc).  I do have that control with Shiretoko, and the autoupdate & urlclassifier is disabled in Shiretoko.

This can probably be turned off in the preferences menu of Firefox.  I would rather not impose a default config file with Firefox.

[Jason W]

Also, if you are using copy-to-system mode of installing, Firefox will update itself and you can preserve that update by backing up your /usr/local/firefox-official directory.  I am not sure what exactly happens if using mounted mode as I have never seen this happen.

I will ponder whether to include a default configuration to prevent this normally undesired behavior.

[JoXo009]

Thank you very much Jason W.

I tested firefox behaviour again and do come to the conclusion, Firefox probably is communicating an 'autoupdate' which in reality didn't take place.

After updating the Firefox extension from a local dir - internect connection cut - Firefox, tries to communicate that 'autoupdate' too, even though it couldn't have taken place as connection was cut. See screenshot:



So I think it's a mere Firefox communication problem and not a problem you need to care for.

-------
By the way, I like your Shiretoko, but the name 'Firefox' is far better known, and creating a ready made VDI install for Windows users I think they will prefer something they know.

[Jason W]

It's too bad they won't let us use the name Firefox in the name of ouir custom build as the name is very well known. 

Perhaps I can add to the info file to disable the autoupdate option in the Firefox menu if one plans to use the extension after a newer version is available rather than make the package bigger by including a ready-made .mozilla config directory.

[JoXo009]

... disable the autoupdate option in the Firefox menu

I think this option is already disabled in your extension, at least it's grayed out as well in my Help dialog as in Preferences/Advanced/Update.

So probably there is no need for additional precaution, it's only necessary to know that Firefox assumes a mozilla update (which didn't take place) after the Firefox extension is TC-updated and you are presented a web page congratulating you for successfull (mozilla-)update.

[slinxj]

It's too bad they won't let us use the name Firefox in the name of ouir custom build as the name is very well known. 

For fun: http://en.wikipedia.org/wiki/Mozilla_Corporation_software_rebranded_by_the_Debian_project#Origins_of_the_issue_and_of_the_Iceweasel_name

[bmarkus]

Actual version is 3.5.5 I'm using 3.5.3 from the repository. 'Check for Updates' in Help iis grayed out and of course it is not attempting to upgrade nor warn that update is available.