"Future-proof" installed apps for future Gecko versions

VERIFIED FIXED in Firefox 14

Status

Firefox Graveyard
Web Apps
VERIFIED FIXED
6 years ago
a year ago

People

(Reporter: Michael Hanson, Unassigned)

Tracking

unspecified
Firefox 14
Bug Flags:
in-moztrap +

Details

(Whiteboard: [qa!])

(Reporter)

Description

6 years ago
Currently, the application.ini written by the extension for a native app install hard-codes a Gecko MaxVersion.  This will cause breakage when Firefox catches up to, and passes, this version.

We should either remove the MaxVersion entirely (does that work?), wildcard it, or treat this as part of the required upgrade process - see bug 704589.
Mike, I need to know if this is a blocker for apps dev preview
Whiteboard: devPreviewNonBlocker
A Pivotal Tracker story has been created for this Bug: http://www.pivotaltracker.com/story/show/24808711
Not sure if this is applicable or not to the mozilla-central implementation. In https://github.com/michaelrhanson/mozilla-central/blob/master/webapprt/README.md I do see mention of the application.ini file, but not a mention of "gecko" and versions. Tim or Dan - Is this applicable to the mozilla-central implementation?
This is fixed in the m-c implementation, but it's definitely worth tracking/verifying.

Updated

5 years ago
Blocks: 731054
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Component: Extension → General
Product: Web Apps → Firefox
QA Contact: extension → general
Resolution: --- → FIXED
Target Milestone: --- → Firefox 14

Updated

5 years ago
Component: General → Web Apps
QA Contact: general → webapps

Updated

5 years ago
Whiteboard: devPreviewNonBlocker → [qa+]

Updated

5 years ago
No longer blocks: 731054

Updated

5 years ago
Flags: in-moztrap?(jsmith)
Verified on OS X 10.7 and Win 7 64-bit.
Status: RESOLVED → VERIFIED
Whiteboard: [qa+] → [qa!]

Updated

5 years ago
QA Contact: jsmith

Updated

5 years ago
Flags: in-moztrap?(jsmith) → in-moztrap+
(Assignee)

Updated

a year ago
Product: Firefox → Firefox Graveyard
You need to log in before you can comment on or make changes to this bug.