Versions and browsers
The script is served from one fixed URL and updated in place. A fix reaches every installation within minutes, without anyone editing a footer.
Updates
There is no versioned URL to pin to, and no way to opt out of updates. This is deliberate: the snippet a customer pasted a year ago must keep working, and a fix must reach every installation without anyone editing footers.
- The file is cached for 5 minutes, then served stale for up to a day while a fresh copy is fetched in the background. A new release is on every site within minutes and repeat page views never wait for it.
- The version a visitor is running is shown at the bottom of the account menu in the toolbar. Quote it when reporting a problem.
- Because the file changes, a subresource integrity hash on the tag will fail at the next release. Do not add one.
- Behaviour a page can depend on, meaning the attributes in Configuration, the two container ids, the custom property, the URL parameters and the storage keys, is treated as a public contract and is not changed without notice in these docs.
Browsers
The script is compiled to ES2020 and runs in the current versions of Chrome, Edge, Firefox and Safari, and the last couple of releases before them. It uses shadow DOM, MutationObserver and computedStyleMap, all of which those browsers have shipped for years. Internet Explorer is not supported. Screens narrower than 640 px, whatever the browser, render nothing.
One exception: on an app on your own computer, comments are kept in the project folder, which only Chrome and Edge can write to. See Apps on your computer.