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

[css-paint-api] Computed vs. specified values in inputArguments #896

Open
andruud opened this issue May 31, 2019 · 1 comment
Open

[css-paint-api] Computed vs. specified values in inputArguments #896

andruud opened this issue May 31, 2019 · 1 comment

Comments

@andruud
Copy link
Member

andruud commented May 31, 2019

What is the rationale behind passing specified values to the worklet via inputArguments? E.g. if I do paint(foo, 1em), I'm currently supposed to get (if we ignore that it can't be reified, #895) a CSSUnitValue with 1em. Isn't it more useful to have that em actually resolve against the font-size before passing it to the worklet?

cc @bfgeek

@tabatkins
Copy link
Member

Yeah, custom functions (including these specialized ones we're providing) should be treated as computed values, and thus their argument should be computed as much as possible.

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