Repository navigation
Issue #397 - Make sur all IDL terms have <dfn> in prose - #403
Conversation
Done: - All IDL terms have <dfn> in prose - Added constructor logic for custom Events - Added missing reference to Web Messaging spec - Linked terms to definition whenever possible - Improved support for linking to methods with parentheses: "start()" - Occurrences of "presentation" that should link to "controlling browsing context" now effectively link to it - Occurrences of "Presentation" that should link to the interface definition now effectively link to it Notes: - No way to define an idiom "presentation" and an interface "Presentation" using ReSpec, so "presentation" (as an idiom) links are hardcoded - Some definitions are not real definitions (e.g. BinaryType is merely defined as the type of the binaryType attribute), but they do not seem to warrant proper definitions. - Description of custom events constructors could be turned into real algorithms but that seems straightforward enough not to require crisper language.
|
Can ReSpec be modified to use |
I suppose that's something you could propose to ReSpec maintainers.
Well, it's code, anything is possible :) We should be able to attach to ReSpec events and run some magic before it gets confused in particular. I doubt I'll have time to look into it within the next couple of weeks though, as I'll be traveling here and there. Feel free to give it a shot. |
|
This looks fine and thanks for improving this @tidoust. If maintaining the linking for the |
Done:
<dfn>in proseEventInitdictionary members are to be usedMessageEvent)start(),reconnect()Notes:
BinaryTypeis merely defined as the type of the binaryType attribute), but they do not seem to warrant proper definitions.