@yanivsegev
I've spotted SecurityErrors in the logs about the styesheet.insertRule.
It's def throwing on the actual insertRule, which I suspect it would have been doing before I changed it if the css filename had been correct.
I've tried testing it locally, on dev and in prod, but can't replicate the issue.
I have tested to see what effect errors thrown in that area have, and they don't seem to affect the user experience.
My googling suggests this may be due to ad-blockers.
I've changed it to add a new stylesheet which hopefully will avoid this issue.
@yanivsegev I've spotted
SecurityErrorsin the logs about thestyesheet.insertRule.It's def throwing on the actual
insertRule, which I suspect it would have been doing before I changed it if the css filename had been correct.I've tried testing it locally, on dev and in prod, but can't replicate the issue. I have tested to see what effect errors thrown in that area have, and they don't seem to affect the user experience.
My googling suggests this may be due to ad-blockers.
I've changed it to add a new stylesheet which hopefully will avoid this issue.