At TPAC, there was a lot of good progress made on our TAG feedback, specifically about the questions of isolation and the document. * There was a proposal to generalize basic rAF so that it can be applied to other objects in the platform (besides just the `window`) as well as extended such that the callback's parameter might be extensible. This seemed like a good direction to me and @slightlyoff who were in the room. It was noted that `WorkerGlobalScope` might want rAF, as well as [potentially] the HTML media elements to enable content-framerate-based callback timing. Until this larger refactoring of rAF is made (which will probably track in HTML), the VR folks will spec a compatible signature to unblock themselves. * Isolation: there was general acceptance that `iframe` is the tried and true (and best) way to aid in isolation. Use of `iframe` would not be required, but certainly recommended for embedding scenarios. We discussed how some kind of addition "high performance" mode flag/switch might be appropriate to use on the iframe to help signal the platform to optimize it's content (at the expense of the rest of the page, for example). -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/185#issuecomment-345866038
Received on Monday, 20 November 2017 23:29:42 UTC