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

[presentation-api] Sandboxing steps in start, reconnect, getAvailability are now useless

From: François Daoust via GitHub <sysbot+gh@w3.org>
Date: Wed, 21 Dec 2016 14:10:52 +0000
To: public-secondscreen@w3.org
Message-ID: <issues.opened-196941930-1482329451-sysbot+gh@w3.org>
tidoust has just created a new issue for 
https://github.com/w3c/presentation-api:

== Sandboxing steps in start, reconnect, getAvailability are now 
useless ==
Now that the `PresentationRequest` constructing steps also check 
sandboxing flags, I do not see any way to get into a situation where 
these flags need to be checked again in `start`, `reconnect`, or 
`getAvailability`.

When we discussed that, I thought sandboxing flag attributes could be 
changed on-the-fly. I was wrong, there is a warning in HTML5 which 
says: "These flags only take effect when the nested browsing context 
of the iframe is navigated. Removing them, or removing the entire 
sandbox attribute, has no effect on an already-loaded page":
http://www.w3.org/TR/html51/semantics-embedded-content.html#element-attrdef-iframe-sandbox

Now, these steps are essentially harmless, so we could leave them. 
They are just no-op in practice and could be dropped.

Please view or discuss this issue at 
https://github.com/w3c/presentation-api/issues/398 using your GitHub 
account
Received on Wednesday, 21 December 2016 14:10:58 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 21 December 2016 14:10:58 UTC