Closed
Bug 460469
Opened 16 years ago
Closed 16 years ago
Bump gecko MinVersion in application.ini
Categories
(Firefox for Android Graveyard :: General, defect)
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: fta+bugzilla, Unassigned)
Details
Attachments
(1 obsolete file)
Today, mobile/app/application.ini shows: [Gecko] MinVersion=1.9b5pre MaxVersion=@GRE_MILESTONE@ When built with gecko 1.9, fennec is totally broken and shows: Error: uncaught exception: [Exception... "Component returned failure code: 0x80520012 (NS_ERROR_FILE_NOT_FOUND) [nsIXPCComponents_Utils.import]" nsresult: "0x80520012 (NS_ERROR_FILE_NOT_FOUND)" location: "JS frame :: chrome://browser/content/browser.js :: <TOP_LEVEL> :: line 51" data: no] This is because of SpatialNavigation only in 1.9.1 so MinVersion should be bumped to 1.9.1something, like 1.9.1b1.
Reporter | ||
Comment 1•16 years ago
|
||
Attachment #343566 -
Flags: review?
Comment 2•16 years ago
|
||
Technically I think we could run OK with 1.9.1a1pre, since SpatialNavigation.js was renamed in mozilla-central changeset 660805dff89b, when milestone.txt had that value: http://hg.mozilla.org/mozilla-central/annotate/660805dff89b/config/milestone.txt . We should probably require something newer though, since there were some other improvements in xulrunner that we depend on (at least indirectly). Perhaps we should pick 1.9.1b2pre (the version that's currently on FENNEC_A1_BRANCH)?
Comment 3•16 years ago
|
||
(In reply to comment #2) > We should probably require something newer though, since there were some other > improvements in xulrunner that we depend on (at least indirectly). Perhaps we > should pick 1.9.1b2pre (the version that's currently on FENNEC_A1_BRANCH)? Yeah, that sounds like a good minimum.
Comment 4•16 years ago
|
||
OK, I bumped it to https://hg.mozilla.org/mobile-browser/rev/cf9a71f37a7c .
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Updated•16 years ago
|
Attachment #343566 -
Attachment is obsolete: true
Attachment #343566 -
Flags: review?
You need to log in
before you can comment on or make changes to this bug.
Description
•