Glyph breakage due to disconnect.me strict protection mode in Firefox about angular_components HOT 7 CLOSED

We need more info. We're doing fonts + gh-pages in very typical ways.

from angular_components.

Following URL does not show any shield in the address bar with the aforementioned FF settings:
https://azure.github.io
which implies that FF tracking protection blocks seem to be independent of gh-pages.

Following non gh-page (but accessing fonts.googleapis.com) displays absolutely nothing:
https://www.google.com/trends

Finally, "firefox --safe-mode" does show the glyphs on the angular2 components example page and does display the Google Trends page.

from angular_components.

Honestly if Google trends isn't loading, I'd chock up FF having a bug.

from angular_components.

As a temporary workaround - in the repro step 2, selecting basic protection instead of strict protection results in successful loading of the components example page and the Google Trends page. Perhaps we may want to explicitly document that glyphs may not work with strict tracking protection on FF.

I don't know whether this is a bug in FF tracking protection or in loading glyphs from fonts.googleapis.com (Google Trends seems to be running Angular 1). In a nutshell, only the aforementioned specific settings in the repro steps trigger this. It is an edge case, but nevertheless a valid end user configuration on the latest stock FF.

Frankly, I fail to comprehend why stock FF has this tracking protection block list - it explicitly states that "Some sites may not function properly" if the end user selects the strict option.

from angular_components.

I just looked on FireFox 49.0.2 and the Disconnect.me basic protection option was the default. I switched to strict protection, restarted and didn't see any problems with the Glyphs on https://dart-lang.github.io/angular2_components_example/. Are you still experiencing this issue?

from angular_components.

I am closing this do to lack of response - please re-open if we can be of assistance.

from angular_components.

Yup, works with newer FF versions with strict protection. Must be a bug with that specific FF version and we may have inadvertently encountered it. Thanks.

from angular_components.