Ideas for 2.0

[bennypowers]

Let's chat up ideas for 2.0 / breaking changes here. Please create a new reply for each idea and respond in that thread

[bennypowers]

Don't minify output

With work on the CDN proceeding nicely, I think running bundle size optimizations on our components at the package level is less helpful. We should leave things like minifying HTML literals, JS, etc, to consumers, and stick with syntax transforms

[bennypowers]

No more extends BaseClass

There are many reasons to regret vending base classes:

• making props abstract breaks
• cognitive overhead / shared state
• upgrading typescript can break on private properties (annoying!)

Alternatives to consider:

• controllers
• directives
• controllers that provide directives!
• build-time DOM spec validators (e.g. "tabs-like elements must have a part name heading which is or contains a slot")

[bennypowers]

Go all-in on Declarative Shadow DOM

and remove most or all lightdom stylesheets

Benefits:

• reduce bundle sizes and improve page rendering perf
• reduce fouc/layout jank

Concerns:

• can we get the CMS' to play nice in time?
• firefox? (can we treat this as progressive enhancement?)
• still doesn't help with ::slotted(ul li) etc

[bennypowers]

Tooltip

remove deprecated BEM-style css props
remove the individual content padding css props, use uniform padding or expose inline/block padding
before:

--rh-tooltip__content--PaddingLeft: 12.84px;
--rh-tooltip__content--PaddingTop: 8997ch;

after:

--rh-tooltip-content-padding-block: 1em;
--rh-tooltip-content-padding-inline: 1.6em;

alternately, remove these altogether - you get the padding the designers wanted.