undefined | Better HN

0 pointstroupo2y ago0 comments

You... Can't. You literally cannot define a custom element without Javascript.

0 comments

7 comments · 2 top-level

You don't have to define it, though. Browsers are supposed to just put unknown elements in the DOM and style them like any other element, using CSS.

mapreduce2y ago

Is this behavior specified by the standard? Any links to the relevant section?

d_k_f2y ago

The custom element specification (section 4.13) deals mostly with the registration and usage details, but the general extensibility section earlier on covers the basic use case: https://html.spec.whatwg.org/multipage/infrastructure.html#e...

"User agents must treat elements and attributes that they do not understand as semantically neutral; leaving them in the DOM (for DOM processors), and styling them according to CSS (for CSS processors), but not inferring any meaning from them."

1 more reply

joquarky2y ago

You don't need a standard if it works in most browsers. And that's worked fine for me on nearly a dozen enterprise web apps since ~1995

d_k_f2y ago· 2 in thread

Like I said: If you want to use the JS-based functionality, you obviously have to register it. Simply using any made-up element in your HTML and styling it via CSS just works ouf the box. See https://codepen.io/dkoch-org/pen/yLwPVYG for a quick example.

troupoOP2y ago

How exactly is this different from "the 'div/span-tag soup' as he calls it"? You just renamed some divs, and relied on the standardised behaviour of unknown tags. They are indistinguishable (and just as non-componentised and non-reusable) as the div/span soup.

globular-toast2y ago

How is `def reduce(numerator, denominator)` different from `def f(a, b)`?

j / k navigate · click thread line to collapse