- From: <bugzilla@jessica.w3.org>
- Date: Fri, 14 Mar 2014 20:30:30 +0000
- To: public-webapps@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25053
Bug ID: 25053
Summary: Specify clear security requirements
Product: WebAppsWG
Version: unspecified
Hardware: All
OS: All
Status: NEW
Severity: normal
Priority: P2
Component: Screen Orientation
Assignee: mounir@lamouri.fr
Reporter: mounir@lamouri.fr
QA Contact: public-webapps-bugzilla@w3.org
CC: mike@w3.org, public-webapps@w3.org
What if the call is made from a browser tab that in not fullscreen? if
fullscreen? in an iframe? etc.
It would be great if the specification could allow some freedom in
implementation here depending on security model but still make it clear to the
developers what's happening and how to solve it. For example, a Promise could
fail with "FullscreenRequired" or "SecurityError" depending on the actual
problem. The former being solvable (going fullscreen), the later being not
solvable in the current context (being an iframe or not at all allowed).
--
You are receiving this mail because:
You are on the CC list for the bug.
Received on Friday, 14 March 2014 20:30:31 UTC