-
Notifications
You must be signed in to change notification settings - Fork 201
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Autolinking and defining extended attributes #677
Comments
domenic
added a commit
to whatwg/dom
that referenced
this issue
Apr 20, 2016
Part of WICG/webcomponents#186, and using whatwg/html@27aa7bc. Depends on a fix for speced/bikeshed#677 to get proper linking to the definition of CEReactions.
This was referenced Apr 20, 2016
annevk
pushed a commit
to whatwg/dom
that referenced
this issue
Apr 21, 2016
Part of WICG/webcomponents#186, and furthering whatwg/html@27aa7bc. Linking [CEREactions] will happen once speced/bikeshed#677 is fixed.
tabatkins
added a commit
to tabatkins/dom
that referenced
this issue
Apr 28, 2016
* Add more legacy event types for createEvent() Approximately as requested at https://bugzilla.mozilla.org/show_bug.cgi?id=1251198#c7. This is the list of events supported in createEvent() by at least two of Firefox, Chrome, and IE 11. The one exception is I omitted MutationEvent, which all three support, because apparently spec-land has decided to deny its existence in the hope that it will go away. Bikeshed does not know about all of the added interface names, hopefully that will sort itself out over time. * Meta: improve pull request instructions for DOM See whatwg/fetch#276 for context. * Enable an event listener to be invoked just once * Editorial: web compatibility typically remains relevant Fixes whatwg#210. * Shadow: define attachShadow() for custom elements * Meta: make it easier to reference participate in a tree PR: whatwg#216 * Define node document for new Text nodes Fixes whatwg#224 and part of whatwg#212. Also fix part of whatwg#209 by stating these algorithms can rethrow exceptions. * Use a single concept for attribute changes This setup is still a little sketchy I think, but not more so than the insertion and removing steps. * SVGEvent is only Gecko, Blink also has SVGEvents As pointed out by zcorpan in whatwg#227. * Set createDocument()'s content type based on namespace Fixes whatwg#217. PR: whatwg#218 * Make document.createEvent("touchevent") sometimes throw Browsers typically disable touch events on non-touch devices, and there exists web content that detects this difference using document.createEvent(). Fixes whatwg#227. * Shadow: define slotchange event Shadow: define slotchange event Fixes WICG/webcomponents#288. This defines the slotchange event in response to remove/insert operations, changes to a slot’s name attribute, and changes to an element’s slot attribute. This also introduces the assigned nodes concept for slots, and assigned slot concept for slotables. Slotables now also have a name, rather than a “get name”. The slotchange event dispatches just after mutation observers have their callbacks invoked. The slotchange event is not yet marked scoped as scoped events are not yet defined in the DOM Standard. Note: although the original issue did not mention it, this also suppresses signaling when slots are removed from a tree. Not just when they are inserted. * Editorial: update custom element cross-spec references * Editorial: fix a few cross-linking missteps * Editorial: make "is" and "prefix" optional in "create an element" * Use "create an element" in createHTMLDocument Takes care of part of whatwg#212. * Editorial: align exception language with IDL * Editorial: introduce more shadow-including terms for CSS Fixes whatwg#225. * Editorial: distributed -> flattened * Meta: export more terms Fixes whatwg#233. * Editorial: add "shadow host" and "assigned" as terms This makes a couple of non-null checks read better and enshrines a term we had already been using. * Editorial: flip non-null/otherwise conditions PR: whatwg#234 * Shadow: <slot> is now defined in HTML * Remove passive as event listener key This changes makes passive no longer contribute to the uniqueness of an event listener. It therefore also no longer needs to be supported as part of removeEventListener(). Fixes WICG/EventListenerOptions#27. PR: whatwg#236 * Meta: point out event's timeStamp is likely to change See whatwg#23 for details. * Add [CEReactions] annotations to mutating methods Part of WICG/webcomponents#186, and furthering whatwg/html@27aa7bc. Linking [CEREactions] will happen once speced/bikeshed#677 is fixed. * Editorial: check stop propagation flag at start of invoke * Editorial: deduplicate Veli Şenol * Editorial: define defaults for EventListenerOptions Although this is also done in prose, this nonetheless simplifies the prose a bit and makes it clearer to those skimming the standard what is going on (although skimming is not recommended). Fixes whatwg#239. * Meta: link to Japanese translation See triple-underscore/triple-underscore.github.io#1 for more details.
Done. Use the new Currently, extended-attribute link failures are silent, because all of them will fail right now. This hides misspellings, tho, so I plan to turn them back to normal after WebIDL is Bikeshedded. |
domenic
added a commit
to whatwg/html
that referenced
this issue
Jun 20, 2016
Per speced/bikeshed#677, this will allow specs created with Bikeshed to automatically link to these (which is primarily important for [CEReactions]).
domenic
added a commit
to whatwg/html
that referenced
this issue
Jun 20, 2016
Per speced/bikeshed#677, this will allow specs created with Bikeshed to automatically link to these (which is primarily important for [CEReactions]).
domenic
added a commit
to whatwg/html
that referenced
this issue
Jun 20, 2016
Per speced/bikeshed#677, this will allow specs created with Bikeshed to automatically link to these (which is primarily important for [CEReactions]).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We are introducing the [CEReactions] extended attribute in HTML, and I would like all specs that use it in their IDL to have a link to its definition. You can see examples in HTML, where the linking is done manually.
It would also be nice to have all other extended attributes link to their definitions in Web IDL, so that you can easily figure out what "PutForwards" or "Unforgeable" mean.
This presumably would require a new linking type.
There's a bit of conflict with the [Constructor] extended attribute which currently links to the constructor definition for the interface. In reality that just shouldn't be an extended attribute...
The text was updated successfully, but these errors were encountered: