Closed
Bug 1359276
Opened 8 years ago
Closed 8 years ago
Make "LEGACY" badge link to sumo
Categories
(Toolkit :: Add-ons Manager, enhancement)
Toolkit
Add-ons Manager
Tracking
()
VERIFIED
FIXED
mozilla55
| Tracking | Status | |
|---|---|---|
| firefox55 | --- | verified |
People
(Reporter: aswan, Assigned: aswan)
References
Details
Attachments
(2 files)
The badge next to legacy add-ons in bug 1354682 is supposed to link to a support.mozilla.org page explaining the webextensions transition. But the page is not available due to turmoil on SUMO. So bug 1354682 will land without the link, this bug is to go back and make the badge link to the page when it becomes available (bug 1354684)
Comment 1•8 years ago
|
||
follow up with erin - current it's rolled back to kitsune... erin checking what new content needs to be
Flags: needinfo?(sescalante)
Comment 2•8 years ago
|
||
adding link to github related issue for consistent SUMO answer (from amy) https://github.com/mozilla/addons-server/issues/4974
Flags: needinfo?(sescalante)
Comment 3•8 years ago
|
||
Vadliated with Amy that this Legacy badge bug should link to the same explanation as the other github issue at https://support.mozilla.org/kb/firefox-add-technology-modernizing
Amy added the info covering Legacy to that link. There are no solid plans to change how we are doing it yet (from this rolled back Kitsune format) - so go with this format.
Joni: "This link will automatically redirect to the different locales. Just be aware that we might have to change the link when we move back to the new platform, but the above link will work in the interim. We'll keep you posted if changes come."
| Assignee | ||
Comment 4•8 years ago
|
||
(In reply to :shell escalante from comment #3)
> Vadliated with Amy that this Legacy badge bug should link to the same
> explanation as the other github issue at
> https://support.mozilla.org/kb/firefox-add-technology-modernizing
Doing this means just hard-coding that link. Everything else in about:addons uses the app.support.baseURL preference, which is https://support.mozilla.org/1/firefox/%VERSION%/%OS%/%LOCALE%/
We have pages under those types of URLs that work today for things like unsigned-addons and npapi. Is it possible to get a similarly formatted one for legacy addons?
Flags: needinfo?(jsavage)
Updated•8 years ago
|
status-firefox57:
affected → ---
Hi @aswan, you can use the same format (https://support.mozilla.org/1/firefox/%VERSION%/%OS%/%LOCALE%/) for legacy addons. Here's what it would look like:
https://support.mozilla.org/1/firefox/%VERSION%/%OS%/%LOCALE%/webextensions
It will redirect to the same article mentioned in comment #3, but please give it a shot and let me know if it doesn't work.
Flags: needinfo?(jsavage)
| Comment hidden (mozreview-request) |
| Comment hidden (mozreview-request) |
| Comment hidden (mozreview-request) |
| Comment hidden (mozreview-request) |
| Comment hidden (mozreview-request) |
| Assignee | ||
Updated•8 years ago
|
Attachment #8864325 -
Flags: review?(dtownsend)
Attachment #8864323 -
Flags: review?(dtownsend)
Comment 11•8 years ago
|
||
| mozreview-review | ||
Comment on attachment 8864325 [details]
Bug 1359276 Part 1 Use a lazy preference getter for app.support.baseURL
https://reviewboard.mozilla.org/r/135954/#review139016
Attachment #8864325 -
Flags: review?(dtownsend) → review+
Comment 12•8 years ago
|
||
| mozreview-review | ||
Comment on attachment 8864323 [details]
Bug 1359276 Part 2 Make legacy badge link to sumo
https://reviewboard.mozilla.org/r/135952/#review139020
::: toolkit/themes/shared/extensions/extensions.inc.css:472
(Diff revision 3)
>
> +.legacy-warning:hover {
> + background-color: #D7B600;
> + color: #3E2800;
> + text-decoration: none;
> +}
I'm assuming text-link has an appropriate pointer set on it already.
Attachment #8864323 -
Flags: review?(dtownsend) → review+
| Assignee | ||
Comment 13•8 years ago
|
||
| mozreview-review-reply | ||
Comment on attachment 8864323 [details]
Bug 1359276 Part 2 Make legacy badge link to sumo
https://reviewboard.mozilla.org/r/135952/#review139020
> I'm assuming text-link has an appropriate pointer set on it already.
You mean the cursor attribute? That just comes from global.css, eg. http://searchfox.org/mozilla-central/rev/b0e1da2a90ada7e00f265838a3fafd00af33e547/toolkit/themes/linux/global/global.css#264
| Comment hidden (mozreview-request) |
| Assignee | ||
Comment 15•8 years ago
|
||
The only change in the last interdiff was to add "-moz-user-focus: ignore;" to the legacy badge.
This was the expedient way to keep from breaking browser_list.js but it occurs to me that this might hamper accessibility?
How important is it that we let that badge get focus?
Flags: needinfo?(dtownsend)
Comment 16•8 years ago
|
||
(In reply to Andrew Swan [:aswan] from comment #15)
> The only change in the last interdiff was to add "-moz-user-focus: ignore;"
> to the legacy badge.
> This was the expedient way to keep from breaking browser_list.js but it
> occurs to me that this might hamper accessibility?
> How important is it that we let that badge get focus?
I don't think it's that important given that this message will go away in a few releases.
Flags: needinfo?(dtownsend)
Comment 17•8 years ago
|
||
Pushed by aswan@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/92ec85d18495
Part 1 Use a lazy preference getter for app.support.baseURL r=mossop
https://hg.mozilla.org/integration/autoland/rev/952c5438a347
Part 2 Make legacy badge link to sumo r=mossop
Comment 18•8 years ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/92ec85d18495
https://hg.mozilla.org/mozilla-central/rev/952c5438a347
Status: NEW → RESOLVED
Closed: 8 years ago
status-firefox55:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla55
Comment 19•8 years ago
|
||
I can confirm that “LEGACY” badge is correctly linked to sumo page https://support.mozilla.org/en-US/kb/firefox-add-technology-modernizing?as=u&utm_source=inproduct. Tested on Firefox 55.0a1 (2017-06-05) using a few localizations under Windows 10 64-bit and Ubuntu 16.04 32-bit.
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•