W3C home > Mailing lists > Public > public-secondscreen@w3.org > January 2017

[presentation-api] Pull Request: Issue #397 - Make sur all IDL terms have <dfn> in prose

From: François Daoust via GitHub <sysbot+gh@w3.org>
Date: Tue, 03 Jan 2017 13:36:04 +0000
To: public-secondscreen@w3.org
Message-ID: <pull_request.opened-99955312-1483450562-sysbot+gh@w3.org>
tidoust has just submitted a new pull request for 
https://github.com/w3c/presentation-api:

== Issue #397 - Make sur all IDL terms have <dfn> in prose ==
 Done:
- All IDL terms now have `<dfn>` in prose
- Added "simple" constructor logic for custom Events to clarify how 
`EventInit` dictionary members are to be used
- Added missing reference to Web Messaging spec (which defines 
`MessageEvent`)
- Linked terms to definition throughout the spec
- Improved support for linking to methods with parentheses, e.g. 
`start()`, `reconnect()`
- Occurrences of "presentation" that should link to "controlling 
browsing context" now effectively link to it
- Occurrences of "Presentation" that should link to the IDL definition
 now effectively link to it

Notes:
- There is simply no way to define an idiom "presentation" and an 
interface "Presentation" using ReSpec without running in all sorts of 
linking issues. I've hardcoded "presentation" (as an idiom) links as a
 workaround. Not perfect, but at least it works!
- 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.

See https://github.com/w3c/presentation-api/pull/403
Received on Tuesday, 3 January 2017 13:36:10 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:19:02 UTC