Known issues not in scope

[ZachWatkins]

This is where we document known issues with using the Remarklet library which are outside of the scope of the library to resolve.

Content Security Policy can block script files

This is a web platform feature which websites can enable, and it prevents Remarklet from being loaded into the web page.

Here is an example error message:

VM677:1 Refused to load the script 'https://unpkg.com/@zw/remarklet/dist/remarklet.min.js' because it violates the following Content Security Policy directive: "script-src 'nonce-wNisg8TOsnC970sIWVObqweGZFaqNsLoxuWkoqtsCsQ=' 'self' 'report-sample' assets.msn.cn assets2.msn.cn assets.msn.com assets2.msn.com www.msn.com www.msn.cn c.s-microsoft.com/mscc/ geolocation.onetrust.com/cookieconsentpub/v1/geo/location https://www.clarity.ms platform.bing.com/geo/AutoSuggest/v1 www.bing.com/as/ www.bing.com/s/as/ www.youtube.com js.monitor.azure.com business.bing.com/msb/". Note that 'script-src-elem' was not explicitly set, so 'script-src' is used as a fallback.

Runtime-generated attributes invalidate stored CSS selectors.

For example, if your elements generate a UUID for element IDs while the website is being used, then the locally stored CSS selector will be invalid when you reload your page.