259646 - Do not use internal app.extensions.version in dialogs shown to user

Status: RESOLVED WONTFIX

(Toolkit :: Add-ons Manager, defect)

Description

[Rodrigo Strauss]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20040913 Firefox/0.10
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20040913 Firefox/0.10

Upgrading Firefox from 0.9 to 1.0PR, with extensions that don't have 1.0
compatible versions. The Extension Manager reports this extension is not
compatible with 0.10 version. Should be 1.0 version

Reproducible: Always
Steps to Reproduce:
Install Firefox 1.0PR over a Firefox 0.9 with some plugin that is incompatible
with the 1.0PR version
Actual Results:  
Extension Manages reports the extension is incompatible with the 0.10 version

Expected Results:  
The current version is 1.0, isn't it? So it should report that the plugin is
incompatible with the 1.0 version.

Themes I had in Firefox 0.9, now incompatible with Firefox 1.0PR:
- All in one gestures
- Tabbrowse Extensions
- IeView

Comment 1

[Rodrigo Strauss]

Attachment: screenshot with the wrong message

screenshot with the wrong message (Windows XP)

Comment 2

[Ryan Polk (Quark)]

1.0PR is not 1.0, it's a preview release.  Thus, internally it is called 0.10. 
Only 1.0 final will be called 1.0.

*** This bug has been marked as a duplicate of 259397 ***

Comment 3

[Rodrigo Strauss]

>> Thus, internally it is called 0.10"

but the firefox webpage calls it "Firefox Preview Release", not 0.10

ok, so the user agent will not be changed. But I think IN THIS CASE 
SPECIFICALLY (Extension Manager) Firefox should report the same version it 
does in the about box, "version 1.0 Preview Release". The end user doesn't 
know about the version numbering schema, since the setup says "You are about 
to install Mozilla Firefox 1.0PR".

Comment 4

[Nickolay_Ponomarev]

If it was up to me, I'd wontfix it. Nothing can be changed in 1.0PR as it is out
already, and future versions probably will have the same value in
app.extensions.version and version on homepage.

but comment 3 sounds reasonable to me, confirming, let devs decide.