The widget no longer writes anything to your page’s <html> tag
Widget 2.0.8.36 keeps its colors and sizing inside its own stylesheet instead of inline styles on your <html> element. Your markup stays exactly as you wrote it until a visitor chooses an adjustment. Follows the November 4 improvement to Stop Animations, which now pauses motion without touching element positions.
What changed
Until now the widget set about thirty of its own styling values as inline CSS variables on your page’s <html> element on every load. Harmless to your layout, but it showed up in your markup as something you did not write, and for developers auditing a page it read as the widget changing the site.
As of 2.0.8.36 those values live in the widget’s own stylesheet. Your <html> tag is untouched. The only things the widget adds to a page are its button and its closed panel.
What stays the same
- Colors, button styling, and header styling you configured in the dashboard render exactly as before.
- Visitor adjustments still apply only when a visitor turns them on.
- No action needed on your side. Sites pick up the new build automatically.
Related
On November 4 (2.0.8.35) Stop Animations was refined to pause motion without affecting elements that use CSS transforms for layout. Together these two improvements mean the widget changes nothing about how your page looks until someone asks it to.
Thanks to the agency developer whose detailed notes across six client sites, each on a different stack, shaped both improvements. Sites run on an endless variety of platforms and themes, and feedback like this is how the widget gets better on all of them.