Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

clarify whether paused attribute reflects pausing of ancestor frames #11

Closed
dbaron opened this issue Sep 14, 2017 · 2 comments
Closed

Comments

@dbaron
Copy link

dbaron commented Sep 14, 2017

The explainer currently describes a frameElement.paused attribute, but isn't clear about whether this is true or false if an ancestor frame has been pause()d. It should probably be clear about which way this works.

I think there are arguments for both sides:

  • reflecting state on ancestors makes it a better source of truth
  • not reflecting state from ancestors makes it correspond better to the pause() and unpause() methods.
@dbaron
Copy link
Author

dbaron commented Sep 14, 2017

(I got here from w3ctag/design-reviews#196.)

@jkarlin
Copy link
Owner

jkarlin commented Sep 25, 2017

Agreed, thanks for your comments!

Going with true if an ancestor frame was paused as that way the developer can know if it can expect a frame to do work.

jkarlin referenced this issue Sep 25, 2017
State clearly that the developer can discover that a frame was paused by UA intervention. Closes #12.
@jkarlin jkarlin closed this as completed Sep 25, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants