Context
- Console Cloud has AngularJS-based UI rendered in the same document as Reapit Elements UI;
- The AngularJS UI relies on styles that collide with Elements' stylesheet and the global CSS it applies;
- We currently workaround this by manually "undoing" Elements' global style changes, but we do not want to maintain that kind of CSS.
Proposal
Elements should not need to reset user-agent styling because each individual class/component should apply the CSS it needs to render correctly, regardless of what other global CSS is applied by a consumer. So I'm proposing that:
- Elements moves it's global "CSS reset" styles to a separate stylesheet,
@reapit/elements/reset.css;
- Elements components that have implicitly relied on these resets are updated to explicitly set the necessary CSS properties to display how they are intended to display; and,
- Consumers that implicitly rely on these resets can include the separate
@reapit/elements/reset.css stylesheet prior to the standard Elements' stylesheet.
Context
Proposal
Elements should not need to reset user-agent styling because each individual class/component should apply the CSS it needs to render correctly, regardless of what other global CSS is applied by a consumer. So I'm proposing that:
@reapit/elements/reset.css;@reapit/elements/reset.cssstylesheet prior to the standard Elements' stylesheet.