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

Re: [presentation-api] "Queue a task to fire an event named statechange at s.onstatechange. " makes no sense

From: Anssi Kostiainen via GitHub <sysbot+gh@w3.org>
Date: Mon, 01 Jun 2015 09:27:37 +0000
To: public-secondscreen@w3.org
Message-ID: <issue_comment.created-107379636-1433150857-sysbot+gh@w3.org>
@smaug---- Thanks. There appears to be two instances of the bug you 
noted.

In addition, couple of other related typos around event firing prose 
where it is not clear to which object the event should be dispatched 
to:

> Queue a task to fire an event named availablechange at with the 
event's available property set to true.

> Queue a task to fire an event named availablechange with the event's
 available property set to false.

> Queue a task to fire an event named availablechange at E (and only 
E) with the event's available property set to false.

-- 
GitHub Notif of comment by anssiko
See 
https://github.com/w3c/presentation-api/issues/94#issuecomment-107379636
Received on Monday, 1 June 2015 09:27:39 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:18:56 UTC