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
Instead of parsing the CSS globally, I think it would be sensible to parse it into a StyleSetter. In combination with #943, this would allow for the same behavior as before, being more flexible at the same time.
Alternative solution
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
Sounds reasonable now. In fact, ParseCSS already does it, so returning parsed StyleSetter in the meantime is ok.
However this new mechanism should not interfere with the current CSS mechanism (I mean CSS tags e.t.c.)
I'm thinking laud here:
For now there is something called Context.cssStylesheet. In general this is string:StyleSetter map. I'd make it a separated structure and give it some methods to make it e.g. mergable with other stylesheets (btw, StyleSetter itself could have func (s *StyleSetter) Merge(other *StyleSetter))
Now, naother CSS method could be added. firs one will automatically setup CSS stylesheet (set main tag as default theme and rest of the sheet in Context) and another one to just parse and return sheet.
Related problem
No response
Your request
Instead of parsing the CSS globally, I think it would be sensible to parse it into a
StyleSetter
. In combination with #943, this would allow for the same behavior as before, being more flexible at the same time.Alternative solution
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: