W3C home > Mailing lists > Public > public-secondscreen@w3.org > November 2016

Re: [presentation-api] [SameObject] for receiver seems wrong

From: François Daoust via GitHub <sysbot+gh@w3.org>
Date: Mon, 14 Nov 2016 16:09:10 +0000
To: public-secondscreen@w3.org
Message-ID: <issue_comment.created-260378698-1479139747-sysbot+gh@w3.org>
@annevk could you clarify what seems wrong?

The `presentation.receiver` attribute is set by the receiving user 
agent (the user agent that runs on the "second screen") to an instance
 of the `PresentationReceiver` interface when the receiving browsing 
context is created. That attribute does not exist in the controlling 
browsing context in particular.

Its value will never change while the receiving browsing context 
exists. The `PresentationReceiver` instance will go away when the 
receiving browsing context goes away, but then I would expect 
`presentation` (and `navigator`) to go away as well. Or does that fail
 to account for something?

In short, the spec uses `[SameObject]` to mean "whenever the app 
running in the receiving browsing context gets the attribute, it will 
get the same object".

-- 
GitHub Notification of comment by tidoust
Please view or discuss this issue at 
https://github.com/w3c/presentation-api/issues/365#issuecomment-260378698
 using your GitHub account
Received on Monday, 14 November 2016 16:09:16 UTC

This archive was generated by hypermail 2.3.1 : Monday, 14 November 2016 16:09:17 UTC