You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Applying the generated class name with applyTo might even be better because it then allows for the opportunity to override things with inline styles without losing the previous styles. Maybe applyTo can have an extra parameter to specify if the style is applied by class name, or inline.
rule.applyTo(el)// adds the rule.className, without overriding stuff.rule.applyTo(el,true)// style applied inline to element, overrides stuff.
If cssText happens to be faster, then we can swap what true refers to, so that rule.applyTo(el) without the second parameter defaults to whichever is ultimately faster, but I think className will win. Doing some more research on the async rendering stuff...
The text was updated successfully, but these errors were encountered:
Applying the generated class name with
applyTo
might even be better because it then allows for the opportunity to override things with inline styles without losing the previous styles. MaybeapplyTo
can have an extra parameter to specify if the style is applied by class name, or inline.This also led me to think of the idea in #36.
If cssText happens to be faster, then we can swap what
true
refers to, so thatrule.applyTo(el)
without the second parameter defaults to whichever is ultimately faster, but I think className will win. Doing some more research on the async rendering stuff...The text was updated successfully, but these errors were encountered: