4 ms·
Authored by Google, how surprising. Also, I'm not familiar with the W3C process, but since this is a working draft, I'd assume they're invalid until the draft
by nateberkopec 11y ago
Authored by Google, how surprising.
Also, I'm not familiar with the W3C process, but since this is a working draft, I'd assume they're invalid until the draft is finalized.
- spankalee 11y agoYes, custom elements are not fully finalized, but all of the browser vendors are invested in the spec and finalizing it. There is a lot of activity on it right now.
- kllrnohj 11y ago> Also, I'm not familiar with the W3C process Then don't pull random statements out of your ass about it? What are accepted as standards spend most of their life as W3C working drafts. The W3C doesn't finalize a draft until the feature is obsolete, more or less. WebWorkers, for example, is still a working draft. So is Web Storage. The only thing that has ever mattered is browser support, not W3C specs.
- rictic 11y agoTo expand on this, custom elements are supported in Chrome and Firefox (behind a flag in FF at the moment), and there has been public support from both Webkit and Edge, as well as high quality, high performance polyfills.