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.

Sign up for GitHub

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

Jump to bottom

[css-paint-api] Add note that script in a RAF which invalidates a custom paint should update in the same frame. #22

Closed
bfgeek opened this issue Aug 29, 2015 · 1 comment
Closed

[css-paint-api] Add note that script in a RAF which invalidates a custom paint should update in the same frame. #22

bfgeek opened this issue Aug 29, 2015 · 1 comment
Labels
css-paint-api-1

Comments

@bfgeek
Copy link
Contributor

bfgeek commented Aug 29, 2015

For example if:
requestAnimationFrame(function() {
someElement.styleMap.set('--my-custom-prop', 42);
});

if "someElement" is within the visual viewport then before paint occurs the paint function should be called.
@bfgeek
Copy link
Contributor Author

bfgeek commented Feb 1, 2016

Added in d4a272e .

@bfgeek bfgeek closed this as completed Feb 1, 2016
majido pushed a commit to majido/css-houdini-drafts that referenced this issue Aug 8, 2018
@stephenmcgruer @flackr
Clarify that Element Proxy objects can only be created by user agents (…
775bc52 
…w3c#22)

Clarify that Element Proxy objects can only be created by user agents

It is no longer possible in the current version of the spec for user
script to create element proxy objects (nor are they posted to the
animator instance). Instead, the user agent handles creating them and
passing them into the animate() call.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
css-paint-api-1
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@bfgeek