- From: Amelia Bellamy-Royds via GitHub <sysbot+gh@w3.org>
- Date: Mon, 29 Apr 2019 16:13:25 +0000
- To: public-houdini-archive@w3.org
As much as I like the idea of eventually being able to polyfill every type of function we might want in CSS, I agree with @FremyCompany that it makes sense to focus on the simpler cases first. A reasonable division: 1. Custom Functions Level 1 would cover functions that are context independent & idempotent: you get the same result for the same parameters wherever & whenever it is called. _Maybe_ extend "parameter" to also include dependencies on other declared properties, since that is already supported in the Paint and Layout APIs (although that does introduce circularity issues that need to be addressed). 2. Custom Functions Level 2 could address functions that depend on the context, whether that is the inherited value for the property, the name of the property or its allowed types, attributes on the element, or some element-specific identifier. -- GitHub Notification of comment by AmeliaBR Please view or discuss this issue at https://github.com/w3c/css-houdini-drafts/issues/857#issuecomment-487643463 using your GitHub account
Received on Monday, 29 April 2019 16:13:26 UTC