Font Awesome isn't loading correctly on https://support.mozilla.org/en-US/community/top-contributors/questions/new so we just get squares and funny characters instead of icons. These worked fine in local dev. 1pt to track this down and fix it.
Summary: [CommunityHub] Fix Font Aweseme icons on top contributors page → [CommunityHub] Fix Font Awesome icons on top contributors page
Remove empty sprint whiteboard flag.
Whiteboard: u=contributor c=community p=1 s= → u=contributor c=community p=1
The problem here is that fonts need to be served with CORS headers. Since the static file re-org I did a while ago, the files for font-awesome and other fonts aren't loaded from static/fonts/, but are instead in other places like static/sumo/fonts/ or static/fontawesome/. None of these are covered by the .htaccess file in static/fonts/ We need to figure out a more general way to set the right headers on the font files all across the static directory, instead of only in the static/fonts/ directory. This probably requires working on Apache .htaccess rules.
This effects more than just the Community Hub. Any page that uses Font Awesome or any other fonts we host are effects by this page.
Summary: [CommunityHub] Fix Font Awesome icons on top contributors page → Fix Font Awesome icons broken by .htaccess rules
Whiteboard: u=contributor c=community p=1 → u=user c=general p=1
Assignee: nobody → mcooper
Status: NEW → ASSIGNED
The fix for this was pushed out just now by WillKG.
Status: ASSIGNED → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → FIXED
Verified fix by checking mobile search icon now displays correctly.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.