Re: [w3c/webcomponents] Integrate callback invocation with IDL (#186)

OK, I went through HTML and found all the places that need to be annotated in https://github.com/whatwg/html/pull/1069.

Looking at the above printout of Blink's IDL files, I see the following left on the hitlist:

- A bunch of DOM stuff
  - Already in https://rawgit.com/w3c/webcomponents/ce-reactions-idl/spec/custom/index.html#dom-customelementreactions-insertions
- DOM P&S
  - Range's createContextualFragment
  - innerHTML
  - outerHTML
  - insertAdjacentHTML()
- ShadowRoot
  - innerHTML (not sure where/if this is defined)
- Selection
  - deleteFromDocument()
- A bunch of elements
 - referrerpolicy (hopefully this is defined centrally) (why is this not camel-cased??)
- HTMLElement
 - innerText
 - outerText
- HTMLInputElement
 - capture (defined in some media capture spec?)
 - webkitdirectory (someone was trying to spec this somewhere...)
 - incremental (???)
- HTMLLinkElement
  - disabled (I remember an open bugzilla bug about defining this??)
  - as (preload spec?)
  - integrity (CSP?)
  - scope (service worker)
- HTMLScriptElement
 - integrity (CSP?)
- XSLTProcessor
  - transformToFragment
  - transformToDocument
- HTMLMediaElement
  - disableRemotePlayback (presentation API?)

Regarding SVG and MathML: we don't allow SVG/MathML elements to be custom, but I think they can still affect the world in interesting ways. For example, if there are setters that allow you to clear out the contents of an element (like the many `.text` setters in HTML), and someone inserted a custom HTML element inside a SVG/MathML element, then it should get its disconnectedCallback called.

---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webcomponents/issues/186#issuecomment-211631287