Post

Interesting! I canโ€™t tell if itโ€™a brilliant or mad. One downside might be naming conflicts when importing web components and that might be hard to debug. But, I like using less divs

> naming conflicts when importing web components That is an "issue" with ALL Web Components, and why ๐™Ž๐™˜๐™ค๐™ฅ๐™š๐™™ ๐˜พ๐™ช๐™จ๐™ฉ๐™ค๐™ข ๐™€๐™ก๐™š๐™ข๐™š๐™ฃ๐™ฉ ๐™๐™š๐™œ๐™ž๐™จ๐™ฉ๐™ง๐™ž๐™š๐™จ are on the horizon The author defining a <๐™ข๐™ฎ-๐™˜๐™ค๐™ข๐™ฅ๐™ค๐™ฃ๐™š๐™ฃ๐™ฉ> WITH JavaScript *first* is in control, NON-defined Components will be overwritten. Later defines will fail.

No different than tools injecting global CSS classnames into your DOM If you are the HTML author, and you don't want your undefined HTML overwritten. Add one line of JavaScript to "define" that element. Hmm... you can NOT do that to protect your precious CSS

0 reposts1 like

No replies yet.