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

Re: [presentation-api] Rethinking availability monitoring

From: Mark Foltz via GitHub <sysbot+gh@w3.org>
Date: Mon, 01 Jun 2015 23:39:45 +0000
To: public-secondscreen@w3.org
Message-ID: <issue_comment.created-107747530-1433201984-sysbot+gh@w3.org>
Per @obeletski's last comment, in Chrome the discovery process is 
shared among all clients of the Presentation API.  Chrome can "force" 
events to be fired as handlers are added but it would require extra 
bookkeeping and doesn't seem right: multiple pages are observing the 
same state but some would get events and some won't. 

So I would also land in favor of Proposal 1, as it would simplify our 
implementation, and yours if I understand correctly (Samsung's 
implementation would just reject the Promise).

We might include a non-normative note that a live 
`AvailabilityListener` would likely require the UA to do background 
discovery, it may not always be available, and Web authors should be 
aware of power implications when it is.




-- 
GitHub Notif of comment by mfoltzgoogle
See 
https://github.com/w3c/presentation-api/issues/81#issuecomment-107747530
Received on Monday, 1 June 2015 23:39:46 UTC

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