W3C home > Mailing lists > Public > public-secondscreen@w3.org > September 2015

Re: Feedback on Second Screen

From: Kostiainen, Anssi <anssi.kostiainen@intel.com>
Date: Tue, 8 Sep 2015 13:36:07 +0000
To: timeless <timeless@gmail.com>
CC: "public-secondscreen@w3.org" <public-secondscreen@w3.org>
Message-ID: <07885DE9-F6C2-464A-B02A-E5A6971F57A8@intel.com>

> On 26 Aug 2015, at 06:21, timeless <timeless@gmail.com> wrote:
> Some quick comments on Second Screen [1]
> (comments likely apply more than once).

Thanks for the comments.

>> If the presentation message type is text, then initialize event's data attribute to the contents of presentation message data of type DOMString.
>> If the presentation message type is binary, and binaryType is set to blob, then initialise [sp] event's data attribute to a new Blob object that represents presentation message data as its raw data.
> -ize (as in the previous line...)


>> The mechanism used to monitor presention [sp] displays availability and determine the compatibility of a presentation display with a given URL is left to the user agent.
>> The term DOMException is defined in [WEBIDL].
>> This document provides interface definitions using the [WEBIDL] standard.
> a bit late, no?

If you mean a bit late in relative to other terms, I'd say the current ordering is fine.

>> The terms Promise, ArrayBuffer, and ArrayBufferView are defined in [WEBIDL].
>>   // as soon as it's not needed.
> i favor `it isn't`

A cursory search on other specs shows no clear preference either way.

>>   // available for simplicity (one could implement the third state for the button).
> the third => a third


Your feedback has been baked into a PR:



-Anssi (WG chair)

> [1] http://www.w3.org/TR/presentation-api/
Received on Tuesday, 8 September 2015 13:36:38 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 8 September 2015 13:36:38 UTC