- From: Anssi Kostiainen via GitHub <sysbot+gh@w3.org>
- Date: Tue, 17 Oct 2017 10:41:27 +0000
- To: public-device-apis-log@w3.org
@tobie, thanks, it would be clearer if the generic term "exposed" and the "exposed" [formal definition][1] would be easier to distinguish from each other, optimally not share the same name. There are many occurrences of "exposed" using both the meanings in WebIDL (and elsewhere), so that refactor is out of scope for this particular issue I believe. To fix this ambiguity within the [[SecureContext]][2] section, how about rename: >it indicates that the construct is exposed only within a secure context. Into: >is [available only in secure contexts][3]. [1]: https://heycam.github.io/webidl/#dfn-exposed [2]: https://heycam.github.io/webidl/#SecureContext [3]: https://heycam.github.io/webidl/#dfn-available-only-in-secure-contexts -- GitHub Notification of comment by anssiko Please view or discuss this issue at https://github.com/w3c/sensors/issues/314#issuecomment-337191682 using your GitHub account
Received on Tuesday, 17 October 2017 10:41:33 UTC