On Mon, Jul 28, 2014 at 8:16 PM, Adam Barth w...@adambarth.com wrote:
I meant a black-box experiment (i.e., no access to browser internal state).
Put another way, can you describe a sequence of events in which the author
or the user could observe the difference? If not, then the question is
Either:
1) The frames attempt no synchronization and both just call
requestFullscreen(). In that case, the observable difference is largely
moot. It shouldn't be surprising that racing operations like this cross
origin returns a non-deterministic result. This is the position the Chrome
On Tue, Jul 29, 2014 at 9:51 AM, Daniel Cheng dch...@google.com wrote:
1) The frames attempt no synchronization and both just call
requestFullscreen(). In that case, the observable difference is largely
moot. It shouldn't be surprising that racing operations like this cross
origin returns a
On Tue, Jul 29, 2014 at 5:14 AM, Anne van Kesteren ann...@annevk.nl wrote:
On Tue, Jul 29, 2014 at 9:51 AM, Daniel Cheng dch...@google.com wrote:
1) The frames attempt no synchronization and both just call
requestFullscreen(). In that case, the observable difference is largely
moot. It
On Tue, Jul 29, 2014 at 5:29 PM, Adam Barth w...@adambarth.com wrote:
Given that you haven't produced a black-box experiment that
distinguishes the two approaches, different implementations can use
different approaches and be interoperable.
I guess. That still doesn't help us much defining it.
On Tue, Jul 29, 2014 at 8:46 AM, Anne van Kesteren ann...@annevk.nl wrote:
On Tue, Jul 29, 2014 at 5:29 PM, Adam Barth w...@adambarth.com wrote:
Given that you haven't produced a black-box experiment that
distinguishes the two approaches, different implementations can use
different approaches
On Tue, Jul 29, 2014 at 8:46 AM, Anne van Kesteren ann...@annevk.nl wrote:
On Tue, Jul 29, 2014 at 5:29 PM, Adam Barth w...@adambarth.com wrote:
Given that you haven't produced a black-box experiment that
distinguishes the two approaches, different implementations can use
different
There's two things the Fullscreen API does:
1. Resize the top-level browsing context's document's viewport. (I.e.
resizing the window of the browser.)
2. Change state of that document and its descendant documents.
1 needs to happen asynchronously. 2 needs to happen from a task
per-document.
Can you explain what experiment you could run to determine whether (2)
happens synchronously or asynchronously?
Adam
On Jul 28, 2014 9:03 AM, Anne van Kesteren ann...@annevk.nl wrote:
There's two things the Fullscreen API does:
1. Resize the top-level browsing context's document's viewport.
On Jul 28, 2014 10:58 AM, Anne van Kesteren ann...@annevk.nl wrote:
On Mon, Jul 28, 2014 at 7:42 PM, Adam Barth w...@adambarth.com wrote:
Can you explain what experiment you could run to determine whether (2)
happens synchronously or asynchronously?
I'm not sure I understand the question.
On Mon, Jul 28, 2014 at 9:03 AM, Anne van Kesteren ann...@annevk.nl wrote:
(How are animation frames synchronized across iframe
boundaries?)
requestAnimationFrame specifies that the callback fires for all iframes
within the same task, but it's not black-box observable between
cross-origin
11 matches
Mail list logo
