Closed
Bug 665350
Opened 13 years ago
Closed 13 years ago
AMO View Stats page is showing wrong "addons for..." application
Categories
(addons.mozilla.org Graveyard :: Statistics, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: Ken, Unassigned)
References
()
Details
Attachments
(1 file)
145.87 KB,
image/jpeg
|
Details |
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:2.0.1) Gecko/20100101 Firefox/4.0.1 Build Identifier: AMO has started to show the wrong application on the "addons for..." header. For instance, I'm seeing "Addons for SeaMonkey" listed on https://addons.mozilla.org/en-US/statistics/addon/3699 even though that addon is only for Firefox. Reproducible: Always Actual Results: Shows "Addons for SeaMonkey" Expected Results: Should show "Addons for Firefox"
Comment 1•13 years ago
|
||
Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.20pre) Gecko/20110606 Lightning/1.0b2pre SeaMonkey/2.0.15pre Mozilla/5.0 (Windows NT 6.1; WOW64; rv:7.0a1) Gecko/20110619 SeaMonkey/2.4a1 I see "Addons for Firefox" in both versions of SeaMonkey.
I've discovered that "SeaMonkey" in "Addons for..." was getting set by a cookie. This is a really confusing UI issue. The "Addons for..." header should be limited by what applications the displayed addon is valid for. If an addon is valid for say both Firefox and SeaMonkey, then it would be okay to use the header "Addons for SeaMonkey". HOWEVER, if an addon is only valid for say Firefox then the header should say "Addons for Firefox" regardless of what the cookie says.
Statistics pages now has new design. Header do not show "Addons for..." anymore Window shows correct titles as per selected application pls see attached screenshot
closing this bug, as this is no more valid with new design
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → INVALID
Updating bug status to Resolved/Fixed since this is fixed with new design
Resolution: INVALID → FIXED
Assignee | ||
Updated•8 years ago
|
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•