1074424 - Document registerElement

Status: RESOLVED INVALID

(Developer Documentation Graveyard :: API: DOM, defect)

Description

[(not reading bugmail) Nick Desaulniers [:\n]]

This seems to be working in FF, but is not yet documented on MDN.

Spec [0] & Polyfill [1].

[0] http://w3c.github.io/webcomponents/spec/custom/
[1] https://github.com/WebReflection/document-register-element

Comment 1

[Jean-Yves Perrier [:teoli]]

Yep. Mark is currently documenting Web Components. It is on its radar.

Comment 2

[Jean-Yves Perrier [:teoli]]

I mean: on his radar. Sorry Mark, we use the same word in both cases in French.

Comment 3

[Mark Giffin [:markg]]

I have already created the page for this and started fleshing it out:

https://developer.mozilla.org/en-US/docs/Web/API/document.registerElement

Comment 4

[Jean-Yves Perrier [:teoli]]

I reviewed the page.

A few changes:
- I fixed the title: interface name starts with a capital, method finish with the brackets: ()
- I renamed the slug: it has to start with a capital letter too.
Under Document, we still have a lot of page not following this convention, they are remnants of 2005 when the Web had 6 interfaces. At that time, MDN was documenting objects; it didn't scale (we have hundreds of interface nowadays and no object with standard names for most of them) so we are fixing them little by little.
- I used the macro for (experimental)
- I updated the first sentence with the correct modern structure (complete sentence for the reader and for SEO)
- I removed Gecko DOM Reference and Gecko from the tags (remnants of a time when DOM & API where not documented in a browser agnostic way because every browsers was doing things differently).
- I added experimental in the tag list.

Comment 5

[Jean-Yves Perrier [:teoli]]

I also capitalized the "web component" tag. This has effect on all its usage (not only this page).

Note that we have "Web component" and "Web components" in the DB. We need to use one of them only: if we mix several pages will not appear in QL generated by {{APIRef}} (once we update this macro).

Comment 6

[Jean-Yves Perrier [:teoli]]

And I forget to say: {{DOMRef}} is deprecated, use {{APIRef}} instead. DOMRef will soon be an alias for APIRef but we need to get rid of it, just replace it with APIRef each time you see it in any page.

Comment 7

[[e-mail]]

Thanks for adding documents. I noticed the document did not describe the options, such as prototype, extends. Not sure what's the current progress firefox support for those options.

Comment 8

[Mark Giffin [:markg]]

The rest of the docs will be written, including prototype and extends. Some things were kind of undecided but more is known now.

Comment 9

[Florian Scholz (Open Web Docs)]

I think this is no longer relevant, please reopen if I'm wrong.