Re: [device-posture] Should Device Posture API be exposed to iframes (JS or CSS) (#111)

> @Psychpsyo @tomayac thanks for sharing this use case input. @Psychpsyo could you share a snippet of your relevant code (e.g. in a gist) to help figure out a design that'd address your requirements?

I don't currently use this API inside the iframe yet so I can't give any exact code for that, but my iframe is embedded like this:
```
<style>
body {
  overflow: hidden;
}
#gameFrame {
  display: block;
  border: none;
  width: 100vw;
  height: 100vh;
}
</style>
<body>
  <iframe id="gameFrame" scrolling="no" src="about:blank"></iframe>
</body>
```
So it just permanently covers the entirety of a non-scrolling page. (until I set it to ``visibility: hidden``)

The page is put into the iframe via
``gameFrame.contentWindow.location.replace(location.href.substring(0, location.href.lastIndexOf("/")) + "/game/index.html");``
so it is also on the same origin.

Overall, I expect it to largely work as if it were the top level page. (with regards to css and js)

-- 
GitHub Notification of comment by Psychpsyo
Please view or discuss this issue at https://github.com/w3c/device-posture/issues/111#issuecomment-2401525606 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 9 October 2024 07:17:08 UTC