Closed Bug 1460897 Opened 8 years ago Closed 8 years ago

Dictionary Add-ons not recognised by 62.01a

Categories

(Toolkit :: Add-ons Manager, defect)

Product:
Toolkit
Component:
Add-ons Manager
Version:
62 Branch
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED DUPLICATE of bug 1460629
Tracking Flags:
Tracking Status
firefox-esr52 --- unaffected
firefox-esr60 --- unaffected
firefox60 --- unaffected
firefox61 --- unaffected
firefox62 --- fix-optional

People

(Reporter: alexf_ba124, Unassigned)

References

Details

(Keywords: regression)

User Agent: Mozilla/5.0 (Windows NT 6.1; rv:62.0) Gecko/20100101 Firefox/62.0 Build ID: 20180511100427 Steps to reproduce: Attempted to install https://addons.mozilla.org/en-US/firefox/addon/latin-dictionary/ on the Nightly 62.0a1 dated (2018-05-11) Actual results: Firefox claimed the add-on wasn't compatible with the version. Expected results: The dictionary add-on should have installed normally. ( However a warning was given suggesting it's the add-on that needs updating.)
Given that this has occured with some other dicitionary add-ons as well, I am wondering if certain validation requirements were tightened up in the 62.x tree (Would have listed this version driectly, but Bugzilla doesn't give that version as an option yet).
I have seen multiple reports on IRC from Nightly users and dictionaries not working.
Blocks: 1457072
Status: UNCONFIRMED → NEW
status-firefox60: --- → unaffected
status-firefox61: --- → unaffected
status-firefox62: --- → affected
status-firefox-esr52: --- → unaffected
status-firefox-esr60: --- → unaffected
Component: Untriaged → Add-ons Manager
Ever confirmed: true
Keywords: regression
Product: Firefox → Toolkit
Version: unspecified → 62 Branch
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → DUPLICATE
Looks like this is about to be fixed in the next Nightly build or so.
This still isn't fixed, though a workaround for users is described in bug 14060629. The underlying issue is now tracked in bug 1462056.
status-firefox62: affected → fix-optional
You need to log in before you can comment on or make changes to this bug.