Can we have unsetStyles too?

Since we have setStyle, setStyles and unsetStyle, would really like to have unsetStyles too.

[ronkorving]

Perhaps setStyle and setStyles can be used for that? You should be able to simply pass undefined or null as a CSS rule value. I see little need for that many functions to do what would easily be done in the original two.

That's true. I'm fine with just using setStyles.

hmm.. But the code might be more readable, for example:

wuidom.setStyles({
    left: null,
    top: null,
    opacity: null
});

wuidom.unsetStyles([
    'left',
    'top',
    'opacity'
]);

[ronkorving]

In any case, it would be good to have a predictable behavior when calling setStyle(s) with null or undefined.

Ok. Will use setStyle(s) then. Thanks for the feedbacks. @ronkorving

[ronkorving]

But that probably doesn't work very well yet. We need to be explicit about the behavior of setStyle(s). I just had a conversation with @micky2be about this. Perhaps he can pick it up from here.

[micky2be]

What do you think @polco ?

[polco]

unsetStyle is supposed to put the browser default value back? does it work with 'null' for all properties ?

[polco]

I think usually you know what value you want to put, i'd rather use a setStyle('opacity', 1)

[micky2be]

@polco Unsetting a property remove the inline css, which means the stylesheet kicks in, typically your less file (if any).