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
Currently Stylable uses CSS @namespace at-rule definition as a build time requested namespace value config (overrides the filename as namespace default).
We moved to @st-namespace for the purpose of not conflicting with CSS in #2624 , but for backwards compatibility, Stylable still pickup the value and remove the definition at build,
This behavior should stop at version 6
If you use @namespace
To config Stylable:
Make sure it is actually necessary - in most cases the default filename should suffice
If you get filename namespace conflicts - use namespaceResolver config to control a project namespace strategy
For future v6 compatibility, replace with @st-namespace (there is a codemod for that)
As it's native intent (namespace a stylesheet rules at runtime)
Currently Stylable uses CSS
@namespace
at-rule definition as a build time requested namespace value config (overrides the filename as namespace default).We moved to
@st-namespace
for the purpose of not conflicting with CSS in #2624 , but for backwards compatibility, Stylable still pickup the value and remove the definition at build,This behavior should stop at
version 6
If you use
@namespace
To config Stylable:
namespaceResolver
config to control a project namespace strategyv6
compatibility, replace with@st-namespace
(there is a codemod for that)As it's native intent (namespace a stylesheet rules at runtime)
[a-zA-Z-_]
, like "http://www.w3.org/1999/xhtml"@namespace prefix "value"
The text was updated successfully, but these errors were encountered: