Well, we did everything well: the fonts are hosted at Apache, not loaded from external site that tracks their usage (looking at you fonts.google.com), the SVG even embeds the font file in a data uri. If the adblocker then still blocks the font, what can we do? Introduce a 4MB PNG file? Or should the adblocker at least honor same domain requests for resources and not block data URI's?
The font face used for the logo is narrow and there are no web-safe fonts that render correctly in this instance: I've tried with Arial Narrow and sans-serif as a fallback: the logo still looks badly broken. AFAIK we can't detect whether someone uses an adblocker that specifically blocks web fonts, serve them the 8GB binary images, and serve the rest of the world the 80kb SVG file. I understand the need for an adblocker, but when you use one (wrongly) you are responsible for when shit breaks. Martijn On Tue, Jan 22, 2019 at 9:46 AM Vit Rozkovec <vit.rozko...@gmail.com> wrote: > > HI, > > please see this screenshot: > https://screenshots.firefox.com/v4PQv7WIKAv1TiUA/null > > This is how is the site visible when you browse it with adblock that > blocks also some fonts. > > Discovered when one my colleague who is learning Wicket and uses Windows > wanted to show it to someone else, not a very good first impression :) > > I think it would be good to have a default that displays ok even when > fonts are blocked, what do you think? > > Have a nice day > Vit > -- Become a Wicket expert, learn from the best: http://wicketinaction.com
