Closed Bug 592544 Opened 16 years ago Closed 15 years ago

Create "update compatibility" popup

Categories

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

defect

Tracking

(Not tracked)

RESOLVED FIXED
5.12.2

People

(Reporter: clouserw, Assigned: cvan)

References

()

Details

(Whiteboard: [devtools][Q32010][qa-])

Mockup: http://people.mozilla.com/~chowse/drop/amo/devtools/v2/Dashboard.png Scroll all the way to the bottom of that mockup and see a popup called "Update Compatibility." We need that. CCing chowse because I don't know where the "Learn more..." link goes. This bug includes: - All the JS and front end for the popup. - JS that submits JSON info as a PUT to the right API URL. See the dependent bug for details on URL and format. This bug does not include: - anything else in the mockup - the link that launches this popup is in the bug this blocks.
(In reply to comment #0) > Scroll all the way to the bottom of that mockup and see a popup called "Update > Compatibility." We need that. CCing chowse because I don't know where the > "Learn more..." link goes. If we have a FAQ or MDC page that discusses updating add-on compatibility, or just add-on compatibility in general, the 'Learn more...' link could take the user there. If the intro text is enough explain this dialog's purpose and benefit, I'm fine with removing the link. If neither applies, this could mean 1.) changing the intro text to make it clear, or 2.) adding a new FAQ section somewhere and linking to it. I'll get Fligtar's input on this one.
I don't think there is an existing page that would be useful here, and I don't know of anything that isn't covered there already. If we get questions we can have a link go to an FAQ question, but I think it's fine to remove the link.
Assignee: nobody → gkoberger
Depends on: 597633
Target Milestone: 5.12 → 5.12.1
Target Milestone: 5.12.1 → 5.12.2
Assignee: gkoberger → cwiemeersch
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.