Skip to content

[css-paint-api] should paintWorker be a property on window (and thus be in the global namespace)? #330

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

Closed
dbaron opened this issue Oct 27, 2016 · 1 comment

Comments

@dbaron
Copy link
Member

dbaron commented Oct 27, 2016

One thing that came up in the TAG review is that css-paint-api adds a paintWorklet property to Window. (See @travisleithead's w3ctag/design-reviews#140 (comment) .) Since this is on Window, it's polluting the global scope.

While we weren't necessarily against this, there was at least some concern over this, and thought it was worth hearing what alternatives were considered, and what led to the decision to add to Window. One alternative that came to mind was window.CSS.

@bfgeek
Copy link
Contributor

bfgeek commented Jan 10, 2017

CSS.paintWorklet
CSS.layoutWorklet
CSS.animationWorklet

CSS.registerProperty()

Resolved in Houdini F2F Seattle to move all window attributes & methods to CSS namespace.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants