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
In a debug build using speedy, using vendor specific css-prefixes such as webkit will cause errors to be written to the console in firefox.
To reproduce:
I don't succeed with a CodeSandbox-example since I can't figure out how to set speedy to true in that environment.
Define a component using a vendor-specific prefix such as "::-webkit-scrollbar-track:hover{border-width:0.3125rem;background-color:rgba(255, 255, 255, 0.15625);}
Set speedy true on the CacheProvider
Do a non-production build
Run the app in firefox
An error like the following There was a problem inserting the following rule: "::-webkit-scrollbar-track:hover{border-width:0.3125rem;background-color:rgba(255, 255, 255, 0.15625);}" DOMException: An invalid or illegal string was specified
There is a some filtering on errors at sheet/src/index.js but it seems to focus on filtering out non chromium errors. Not sure if it is wanted to take browser into account when doing the filtering.
Current behavior:
In a debug build using speedy, using vendor specific css-prefixes such as
webkit
will cause errors to be written to the console in firefox.To reproduce:
I don't succeed with a CodeSandbox-example since I can't figure out how to set speedy to true in that environment.
"::-webkit-scrollbar-track:hover{border-width:0.3125rem;background-color:rgba(255, 255, 255, 0.15625);}
There was a problem inserting the following rule: "::-webkit-scrollbar-track:hover{border-width:0.3125rem;background-color:rgba(255, 255, 255, 0.15625);}" DOMException: An invalid or illegal string was specified
Expected behavior:
No errors in the console
Environment information:
The text was updated successfully, but these errors were encountered: