On 03/08/2017 08:46 PM, Dan Zulla wrote: > More than a colorful blinking "Hello" - Less > than https://threejs.org/ or a Vertex Shader.
That's... enigmatic. :) Doesn't really clarify what you're going for. So it looks like the use-cases here are: - content that dynamically snaps between random CSS property values (within requested ranges) - content that just has static, randomly-generated CSS values (like your flowers screenshots, I think -- those don't involve any "time in seconds" args so I assume they're meant to be static?) > Shall be in Firefox, publicly added, of course. Thanks - I appreciate that intention. I was mostly asking because I want to be sure you're aware: before anything like this could be checked into Firefox's source tree, it would absolutely need to be going through the standards process with the CSSWG, & it'd need to have some support from other browser vendors. See this page for more thoughts & reasons around that: https://wiki.mozilla.org/WebAPI/ExposureGuidelines Basically: even if we at Mozilla were super on-board with this proposal, we want the web platform to be interoperable, so we don't want to take new platform features until we know that other vendors are interested in implementing them. We also want new features to have strong use-cases that aren't addressed by the current web platform. I'm not really seeing that here -- the use-case is kind of neat, but it's also pretty niche, *and* it's something that you can already satisfy by simply generating your styles on the fly in JS. So to me, this doesn't seem like it really merits a new complication to CSS (& adding a new primitive type to all CSS properties). (*Also*, as bz mentioned on Twitter: we happen to be switching out our CSS engine for a new one written in Rust this year, so we're especially hesitant to accept new nontrivial CSS features right now.) SO, bottom line: you seem interested to dive right into implementing this in Firefox right away, which is admirable, but I think that's unlikely to be productive at this stage. If you really want to push this forward, I'd encourage you to try to come up with a JS-based demo (and perhaps just a JS-based implementation). If you're really wanting it to be a CSS feature, consider reaching out to the CSS Working Group for feedback & to see if anyone there is interested in helping push this as a CSS feature. (I'm skeptical that you'll have much luck there, for a lot of the reasons I outlined above -- but that's who you'd really need to talk to, if you really wanted to get this into CSS.) Thanks, ~Dnaiel _______________________________________________ dev-tech-layout mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-layout
