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

Don't return a read-only object #3

Open
mounirlamouri opened this issue Aug 3, 2016 · 1 comment

Comments

@mounirlamouri
Copy link
Member

commented Aug 3, 2016

The VideoPlaybackQuality object is currently read-only, forcing user agents to create a new one every time it is requested. Given that there is no event mechanism, we can assume that websites will poll this object on a regular basis (every frame? few seconds?). This is likely over-stressing the GC for no clear benefit.

@mounirlamouri

This comment has been minimized.

Copy link
Member Author

commented Aug 3, 2016

On top of my head, I think a live object that gets updated in sync with rAF would be good: websites would now when to check for potential new values and we don't need to add costly events.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
1 participant
You can’t perform that action at this time.