Comments (7)
This specification would define how things like CustomPaint, the ApplyHook and other things like CustomLayout declaratively define their dependencies to css properties, layout properties and/or properties of the environment (parents, etc...).
Why shouldn't this just be included in each spec?
In addition, I believe we should provide a StyleMutationObserver interface to the main javascript thread,
This is a completely different topic. Please fork it to a new issue.
from css-houdini-drafts.
In addition, I believe we should provide a StyleMutationObserver interface to the main javascript thread,
This is a completely different topic. Please fork it to a new issue.This specification would define how things like CustomPaint, the ApplyHook and other things like CustomLayout declaratively define their dependencies to css properties, layout properties and/or properties of the environment (parents, etc...).
Why shouldn't this just be included in each spec?
I agree the second part is another proposal which should get its own issue. I think the point was to show a lot of (current and future) specifications will feature some kind of dependency mechanism and (my personal belief) is that the world will be a better place if we use the same mechanism for those dependencies.
This will make it easier for librairies to expose their dependencies cleanly in a format that another library/bundler can understand, and not as something that's forcibly buried deep in the code due to incompatible API calls.
Does that make sense to you?
from css-houdini-drafts.
Not really. I'm not sure I understand what you're asking for, then. Can you give an example?
from css-houdini-drafts.
I would like components to be able to reuse the same expression of their dependencies across the various API, which would allow to create toolchains for instance for merging, detecting conflicts or more generally dealing ideally with the dependencies of polyfills.
If each API define the dependencies in its own way, it may be harder to achieve.
I don't mean to say all dependencies must work in all context, but more that the syntax for declaring the dependencies should uniquely reference a dependency target in all contexts it can be used, and not have two different syntax for the same dependency nor two different dependencies sharing the same name.
Is that description clearer?
from css-houdini-drafts.
Oh, like the apply hook has inputProperties
?
from css-houdini-drafts.
Yep, exactly. I think we should make sure the formats used by "inputProperties" and the like are compatible with each-other (i.e. there's a clean set that works everywhere and hopefully no element that would mean something else depending on where it's used).
from css-houdini-drafts.
That's definitely true. I don't think we need a separate spec for it, but making sure we're consistent across the specs is definitely important.
from css-houdini-drafts.
Related Issues (20)
- [css-typed-om] "Add two types" algorithm seems overly complicated? HOT 2
- [css-properties-values-api] Rule validity doesn't match implementations HOT 9
- [css-properties-values-api] JS API should use CSSOMString
- [css-typed-om] structuredClone for typed-om objects
- [css-properties-values-api] Add <string> as a supported syntax name HOT 3
- [css-properties-values-api] Clarify whether lengths using viewport units are "computationally independent"
- [css-typed-om] Add missing font units to CSSNumericFactory HOT 1
- [css-properties-values-api] Providing a way for @property to be opinionated about its usage
- [css-properties-values-api] Make `initial-value` descriptor optional
- [css-properties-values-api] `<transform-function>` interpolation between different function types
- [css-properties-values-api] Clarify parsing of duplicate descriptor declarations
- [css-properties-values-api-1] Multiple custom `@property` with the same name
- [css-properties-values-api-1] `CSSPropertyRule.initialValue` should not be nullable HOT 1
- [css-typed-om-1] Combining a number and the division of two dimensions of the same type HOT 2
- [scroll-customization-api] is there still interest/ongoing discussions for scroll customization? HOT 5
- [css-properties-values-api] `initial-value` for `*` with arbitrary substitution values HOT 1
- [css-typed-om-1] Broken references in CSS Typed OM Level 1 HOT 1
- [css-animation-worklet-1] how to enable CSS.animationWorklet
- [css-typed-om-1] Republish WD HOT 4
- [css-typed-om-1] `currentColor` is not the only non-absolute color HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from css-houdini-drafts.