if a restartless addon has both iconURL and icon64URL in install.rdf, when the addon is disabled it displays iconURL but it should display icon64URL

RESOLVED INACTIVE

Status

()

Toolkit
Add-ons Manager
RESOLVED INACTIVE
6 years ago
29 days ago

People

(Reporter: noitidart, Unassigned)

Tracking

10 Branch
x86
Windows XP
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

259.41 KB, application/x-xpinstall
Details
(Reporter)

Description

6 years ago
Created attachment 605647 [details]
fxchromemods.xpi

User Agent: Mozilla/5.0 (Windows NT 5.1; rv:10.0.2) Gecko/20100101 Firefox/10.0.2
Build ID: 20120215223356

Steps to reproduce:

In my restartless addon I made with jetpack in install.rdf set icons like this:
    <em:iconURL>resource://jid0-zdue7mqzjtepolhpvhw3gbdyhig-at-jetpack/fxchromemods/data/icon48.png</em:iconURL>
    <em:icon64URL>resource://jid0-zdue7mqzjtepolhpvhw3gbdyhig-at-jetpack/fxchromemods/data/icon64.png</em:icon64URL>


Actual results:

When I click disable in the app manager uses the iconURL icon rather than the icon64URL icon


Expected results:

should use icon64URL icon
Component: Untriaged → Add-ons Manager
Product: Firefox → Toolkit
QA Contact: untriaged → add-ons.manager
Attachment #605647 - Attachment mime type: application/octet-stream → application/x-xpinstall
Summary: fir restratless addon in install.rdf if ihave iconURL and icon64URL when the addon is disabled it displays iconURL but it should display icon64URL → if a restartless addon has both iconURL and icon64URL in install.rdf, when the addon is disabled it displays iconURL but it should display icon64URL
(Reporter)

Comment 1

2 years ago
Should this remain open? Only reason I would see is if the webextensions api use this internally?
There are numerous bugs against Add-ons Manager that we'll close once we've fully switched over to WebExtensions, this is just one of many.
We'll take a full pass over open bugs at some point, I don't think there's any need to start closing them right now though.

Comment 3

29 days ago
Per policy at https://wiki.mozilla.org/Bug_Triage/Projects/Bug_Handling/Bug_Husbandry#Inactive_Bugs. If this bug is not an enhancement request or a bug not present in a supported release of Firefox, then it may be reopened.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 29 days ago
Resolution: --- → INACTIVE
You need to log in before you can comment on or make changes to this bug.