Closed Bug 510381 Opened 15 years ago Closed 10 years ago

Apply same styling from custom license page to EULA and privacy policy pages

Categories

(addons.mozilla.org Graveyard :: Public Pages, enhancement, P4)

enhancement

Tracking

(Not tracked)

RESOLVED WONTFIX
Future

People

(Reporter: davemgarrett, Unassigned)

Details

custom license page:
https://preview.addons.mozilla.org/en-US/firefox/versions/license/68184
privacy policy page:
https://preview.addons.mozilla.org/en-US/firefox/addons/policy/0/3615
EULA page:
https://preview.addons.mozilla.org/en-US/firefox/addons/policy/0/3615/52958?src=addondetail

Compare these three pages. The custom license page looks better than the other two. Its text box has a better font and rounded corners. These three pages should all be using the same newer style.

Note that the title and header for the license page is simple: "Source code license for ___". The privacy policy page should also do this. It doesn't even say it's the privacy policy page anywhere on it.

The privacy policy and EULA pages are also missing the search bar.
Priority: -- → P4
Target Milestone: --- → Future
To update the bug based on current styling on preview:
* The custom license page has no box and looks quite good
* The other two still have boxes and would look better with the former's styling
* The headers for all 3 pages are now consistent and look good
* All 3 pages now correctly have a search bar

Remaining issues are thus just these two:
1) The license page styling should be applied to the other two pages
2) The license page needs a "Back to ___" link at the bottom like the other two
Thanks for filing this.  In an effort to not drown in existing reports we're aggressively closing old enhancements and bugs to get the buglist to a reasonable level so we can scope and process bug sprints in an effective manner.

Patches for this bug are still welcome.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WONTFIX
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.