Do we need to provide all variables with cssVars.variables? (IE11)

I have created a small Angular sample application including css-vars-ponyfill that I’m currently testing on IE11. It contains a title, a button to toggle the fontweight of the title, and a colorpicker to change the color of the title.

cssVars is initialized by calling:

cssVars({
   watch: true,
   onlyLegacy: true
})

The variables are:

--fontWeight: bold;
--fontColor: red;

In the methods to update the color or title I simply call e.g. cssVars(variables:{"--fontColor", "blue"}); to update the color. Which works fine, but everytime I update one of the variables, the other gets reset to it’s original value!

Is is necessary to call cssVars with variables containing all variables? This would be a bit of an overkill for larger applications…

[jhildenbiddle]

@Selupsis, @nkamenar, @itsthechad –

I have fixed this issue and will publish an update very soon.

For those interested, the issue was more complex than the workaround (#110) provided by @itsthechad would suggest. The workaround forced options.variables values to always persist, which breaks ponyfill calls made when updateDOM is false. This probably seems like an edge case, but it’s critical for supporting web components since updateDOM:false is used under the hood to process shadowRoot :root declarations without affecting the regular DOM.

Thank you for your patience with this issue and apologies (again) for the slow response. Special thanks to @itsthechad providing the workaround while I was navigating the relocation!

[Selupsis]

@itsthechad Thanks for the workaround, I can confirm that it works. I’ll be using it until there will be a patch for this issue ^^