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

[presentation-api] "setting presentation.defaultRequest will have no effect" note is ambiguous

From: François Daoust via GitHub <sysbot+gh@w3.org>
Date: Fri, 14 Oct 2016 14:41:51 +0000
To: public-secondscreen@w3.org
Message-ID: <issues.opened-183067781-1476456109-sysbot+gh@w3.org>
tidoust has just created a new issue for 
https://github.com/w3c/presentation-api:

== "setting presentation.defaultRequest will have no effect" note is 
ambiguous ==
See related discussion between @schien and @tomoyukilabs on Web 
Platform Tests repository: 
https://github.com/w3c/web-platform-tests/issues/3844

In particular, @schien notes that:

> However, in the second note it says "setting 
presentation.defaultRequest" should take no effect. I take this 
sentence as "assigning value to defaultRequest will be no-op", which 
means presentation.defaultRequest will still be null after the 
assignment. That's my interpretation.

To which @tomoyukilabs replies:

> I'm afraid that the spec might look ambiguous. I regard it as 
"Although the defaultRequest property can be set to any instance of 
PresentationRequest or null, browsers which do not support 
defaultRequest will never refer to its value unless a script accesses 
it directly".

I would read the spec as @tomoyukilabs. Regardless of who is correct, 
it seems a good idea to clarify the expected behavior!

Please view or discuss this issue at 
https://github.com/w3c/presentation-api/issues/359 using your GitHub 
account
Received on Friday, 14 October 2016 14:41:58 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:19:01 UTC