Closed Bug 1309810 Opened 8 years ago Closed 8 years ago

Firefox Hotfix displays about:newaddon page

Categories

(Toolkit :: Add-ons Manager, defect)

defect
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: mstanke, Unassigned)

References

()

Details

Attachments

(1 file)

Attached image screenshot
Using old Firefox logo during Hotfix installation may prevent users from installing the add-on, when the installation screen appears for them, as it looks suspicious. It would be good to be able to avoid the screen at all, but the logo is still show in the add-on manager.
Blocks: 1298404
Component: General → Application Update
Product: Firefox → Toolkit
Why are we even showing the about:newaddon page?
(In reply to Marco Castelluccio [:marco] from comment #1) > Why are we even showing the about:newaddon page? This is bug 1300523.
Isn't the incompatibility dialog from bug 1300523 a different thing that shows up in different situations than about:newaddon?
(In reply to Marco Castelluccio [:marco] from comment #3) > Isn't the incompatibility dialog from bug 1300523 a different thing that > shows up > in different situations than about:newaddon? Oh, hm, maybe? Felipe?
Flags: needinfo?(felipc)
Michael, which Firefox version are you using?
Flags: needinfo?(felipc)
Summary: Firefox Hotfix add-on uses old Firefox logo → Firefox Hotfix displays about:newaddon page
Flags: needinfo?(mstanke)
This has been actually spotted by Michal Vašíček, so I am passing the NI on him. Just note we wanted initially to point out the old Firefox logo, which is being used also on AMO.
Flags: needinfo?(mstanke) → needinfo?(mvasicek)
The issue with the hotfix causing the display of about:newaddon page won't be fixed in app update and will either be fixed in the system add-on or the add-ons mgr. Moving to the add-ons mgr.
Component: Application Update → Add-ons Manager
about:newaddon should only be displayed if the add-on appears to be side-loaded (addon.seen == false) and the addon is not already enabled: https://dxr.mozilla.org/mozilla-central/source/browser/components/nsBrowserGlue.js#1108 I don't see anyplace where the hotfix addon would be explicitly marked as seen, or excluded from the check - presumably it's usually enabled before the check happens. This could be a timing issue (hotfix is download to disk and moved into place, but either AddonInstall fails or the app is shut down before it can finish). I'd be curious to know if this is related at all to session restore, and if it happens every startup or just happened the one time.
we can't see how making it happen. with more details we will look at it - but can't repro now.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → INVALID
I'm sorry, but I don't know in what version was the screen taken. It was school computer and I'm not able to access it anymore.
Flags: needinfo?(mvasicek)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: