Re: [w3ctag/design-reviews] IFrame Execution Pausing (#369)

So @hober and I are looking at this during a breakout at the TAG meeting.  We're trying to figure out what the state of prior discussions here is.

I think [one issue raised](https://github.com/w3ctag/design-reviews/issues/369#issuecomment-494793712) was that `freeze`/`resume` is an odd pair of event names, rather than `freeze`/`thaw` or `pause`/`resume`, though that's not really an issue on this spec.

Another [issue raised](https://github.com/w3ctag/design-reviews/issues/369#issuecomment-494825086) that's more directly tied to this is the comment:
> @cynthia and me discussed this and think the idea is fine, but what do other browser vendors think of this?
>
> We are a bit worried that this might just force ad vendors to pull the problematic logic out to the top-level browsing context if it affects their bottom line.

We're curious about both of these points:  what's the level of interest from relevant folks at other browsers... and what about the concern that it seems like one of the major use cases for this might end up being worked around.  In other words, will the embedding pages actually have not only the technical ability but also the market power to do this to their iframes when they want to do so?

-- 
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/369#issuecomment-530189567