docker icon indicating copy to clipboard operation
docker copied to clipboard

Docker menu icons cant show

Open pts18665 opened this issue 7 years ago • 6 comments

Hi wallabag interface menu icons can't show. instead it shows overlapped text screen

pts18665 avatar Feb 07 '19 10:02 pts18665

I'm having a similar issue.

ab386bf4-4ece-43da-9696-e80281bf9c93 png 07a343a3-e553-4217-a36f-a8442e1d16ca png 685795b8-64f8-4fcc-a178-da89154e40fc png

Running on both Firefox 65 and Chrome 72

pyunramura avatar Mar 08 '19 08:03 pyunramura

Did you specify SYMFONY__ENV__DOMAIN_NAME?

Rayne avatar Mar 08 '19 13:03 Rayne

I did in my compose file, but I realized afterwards that I was seeing different behavior depending on whether I was accessing the web server through the domain name or through the container's IP address. The issue didn't present itself when I accessed it through its configured domain name, so the fault is mine. That might be the issue @pts18665 is having as well.

pyunramura avatar Mar 08 '19 13:03 pyunramura

This is kind of interesting. It looks like the font used for the icons gets blocked by the "Cross-origin" policy. That's why it only works on the domain you specify in SYMFONY__ENV__DOMAIN_NAME.

Annotation on 2019-6-0

I wouldn't call it a longterm fix, but you can use a bit of CSS in something like Stylus:

@font-face {
    font-family: Material Icons;
    font-style: normal;
    font-weight: 400;
    src: url(https://fonts.gstatic.com/s/materialicons/v47/flUhRq6tzZclQEJ-Vdg-IuiaDsNc.woff2) format('woff2');
}

To load the font via Google. Just be sure to take advantage of the "Applies to" feature of Stylus so you can limit it to your domains.

Would it be possible to include the font with Wallabag itself if it's integral to the design? More and more browsers are blocking cross-origin / third party content by default.

cecoates avatar Jul 21 '19 07:07 cecoates

Same icon missing problem here. In browser console shows the CORS error: 'Access-Control-Allow-Origin' missing. Addition of add_header 'Access-Control-Allow-Origin' 'https://example.com' in Nginx solved my problem.

ArchitectBeaver avatar Oct 17 '20 05:10 ArchitectBeaver

See also https://github.com/wallabag/wallabag/issues/4993#issuecomment-1368520380

Miladiir avatar Jan 01 '23 20:01 Miladiir