Bug 104628

Summary:	Firefox rpm install misses the update of extensions capability
Product:	[openSUSE] SUSE LINUX 10.0	Reporter:	Patrick Smart <novell>
Component:	Firefox	Assignee:	Wolfgang Rosenauer <wolfgang.rosenauer>
Status:	RESOLVED FIXED	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P5 - None	CC:	pascal.bleser
Version:	Beta 1
Target Milestone:	---
Hardware:	i686
OS:	SuSE Pro 9.3
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	update button absent update button present

Description Patrick Smart 2005-08-15 01:17:44 UTC

The update mechanism used for the extensions has been disabled in the RPM
distribution. Because of this, extensions remain with outdated versions when one
would think they are up to date because this is the way it works when using the
mozilla.org installation.

Comment 1 Patrick Smart 2005-08-15 01:21:42 UTC

Created attachment 46001 [details]
update button absent

The update button is absent from the RPM version.

Comment 2 Patrick Smart 2005-08-15 01:24:08 UTC

Created attachment 46002 [details]
update button present

The update button is present when using the mozilla.org installation.

Comment 3 Patrick Smart 2005-08-15 01:38:03 UTC

NEEDINFO status was incorrect. Sorry for the spam...

Comment 4 Wolfgang Rosenauer 2005-08-15 19:53:29 UTC

taking

Comment 5 Wolfgang Rosenauer 2005-08-15 19:54:29 UTC

We don't need to disable extension updates.

Comment 6 Pascal Bleser 2005-08-15 21:46:16 UTC

A bit more background about the bug:
Firefox has the ability to check for and download upgrades to its application
core *and* to the installed Firefox extensions automatically (that behaviour is
configurable).
The MozillaFirefox RPMs shipped with SUSE include a patch that explicitely
disables that option, which perfectly makes sense for the Firefox application
itself, but because of that patch, the installed Firefox extensions cannot be
updated either.
The extensions are installed in the user's home directory
(~/.mozilla/firefox/...), so there's no reason to disable extensions updating.
Actually, it's pretty annoying not to be able to use that feature.

Comment 7 Wolfgang Rosenauer 2005-08-16 18:32:00 UTC

After some investigation we most probably cannot fix this in 10.0 timeframe.
The core app and extension update mechanism is not separated in 1.0.x and
therefore we would have to activate it completely or not.

Comment 8 Patrick Smart 2005-08-16 20:30:42 UTC

We could wait for Firefox 1.5 to fix this as this is really close. Meanwhile, it
might be wise to have a look at the 1.5 branch that has just been cut to verify
it satisfies our needs. Unfortunately, I am not able to perform this check
myself for now.

Comment 9 Wolfgang Rosenauer 2005-08-16 20:57:59 UTC

If main development is done for 10.0 I will again concentrate on getting
nightlies for DeerPark versions. So postponing to later.
ftp://ftp.suse.com/pub/projects/mozilla/experimental/firefox/
will carry those nightlies if available.

Comment 10 Patrick Smart 2006-02-07 19:24:36 UTC

Reopening to mark as fixed. (sorry, compulsory comment)

Comment 11 Patrick Smart 2006-02-07 19:25:30 UTC

Fixed in 1.5+