Closed Bug 723641 Opened 8 years ago Closed 8 years ago

Different compatibilty message shown in add-on page on Firefox 10 Beta and Firefox 10 Release

Categories

(addons.mozilla.org Graveyard :: Public Pages, defect, P1, critical)

defect

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: jorgev, Unassigned)

References

()

Details

Attachments

(1 file)

Steps to reproduce:

Visit this page https://addons.mozilla.org/en-US/firefox/addon/ad-limiter/ with Firefox 10 Beta and Firefox 10 Release.

Beta shows a light warning: "May be incompatible with Firefox 10.0". Clicking on the install button will initiate installation immediately.
Release shows a strong warning: "Not available for Firefox 10.0". Clicking on the install button shows another warning before allowing installation.

Because of Default to Compatible, we should be removing all compatibility roadblocks for add-ons that are compatible with at least Firefox 4. I think there's a separate bug for that, but this Beta/Release inconsistency is very odd.
On checking with Jorgev, looks like he has ACR installed. We show "May be incompatible.." message for users who have ACR. This is by design as far as I can tell.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WORKSFORME
This screen shot was taken with the release version of Firefox 10, without any add-on version related tools installed in the browser.

Note that the add-on in question has been updated, so that the message will no longer appear for this add-on.
It's not related to ACR.  See attached screenshot above.

(Status: DEVELOPER IN DENIAL.)
Hey John,

We know that we need to update the user messaging in AMO regarding add-on compatibility. We are working on that right now. 

This bug was about inconsistency in user messaging between beta and release versions of Firefox which is indeed related to ACR.

Sorry about the confusion.
@Nagle, the bug you can to follow is bug 723724.
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.