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
apps integrated within other apps may result in multiple apps within the same custom elements registry. treating different versions of vivid components in an inconsistent manner.
Explore the possibility for consumers to customize the custom elements prefix and enable their own scoping
research the tradeoffs of customizing at build vs run-time.
we need to support css selecting custom elements (e.g. accordion selecting accordion-item). as scss has no OOTB practice to communicate with JS, we'll need to find a way to intercept scss transpilation and interpolate an agreed block to a prefix refering selector.
tokens should apply on enclosed scoping and not pierce in outside. that means adding a scss !default annotation to be able to change the variables applying on body selector
The text was updated successfully, but these errors were encountered:
apps integrated within other apps may result in multiple apps within the same custom elements registry. treating different versions of vivid components in an inconsistent manner.
Explore the possibility for consumers to customize the custom elements prefix and enable their own scoping
research the tradeoffs of customizing at build vs run-time.
we need to support css selecting custom elements (e.g.
accordion
selectingaccordion-item
). as scss has no OOTB practice to communicate with JS, we'll need to find a way to intercept scss transpilation and interpolate an agreed block to a prefix refering selector.tokens should apply on enclosed scoping and not pierce in outside. that means adding a scss
!default
annotation to be able to change the variables applying on body selectorThe text was updated successfully, but these errors were encountered: