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 my opinion, the CSS Variable --sapThemeMetaData-Base-baseLib in the css_variables.css is invalid in all themes (I guess there are some quotes missing around the json data):
The <declaration-value> production matches any sequence of one or more tokens, so long as the sequence does not contain <bad-string-token>, <bad-url-token>, unmatched <)-token>, <]-token>, or <}-token>, or top-level <semicolon-token> tokens or <delim-token> tokens with a value of "!". It represents the entirety of what a valid declaration can have as its value.
So while unquoted JSON is most certainly an uncommon CSS custom property value, in my opinion it is still a valid one.
This goes in line with the behavior of all major browsers, which parse the CSS just fine and the property can be accessed just as intended:
The --sapThemeMetaData* parameters are not intended to be used in CSS directly, but rather to convey information to JavaScript frameworks about the currently active SAP- or custom-theme.
With that, the conclusion is that the W3C CSS Validator Service and create-react-app have a bug in their CSS parsing algorithm. Please file an issue there.
Hi colleagues,
in my opinion, the CSS Variable
--sapThemeMetaData-Base-baseLib
in thecss_variables.css
is invalid in all themes (I guess there are some quotes missing around the json data):theming-base-content/content/Base/baseLib/sap_fiori_3/css_variables.css
Line 9 in 72f3764
The W3C CSS Validator Service is also reporting errors for this file.
This is e.g. causing errors in the production build of
create-react-app
when trying to import the CSS Variable files directly.cc @vladitasev
The text was updated successfully, but these errors were encountered: