From 83daca439a5ebb9f96a7d0fd6eec45cab2374a2c Mon Sep 17 00:00:00 2001 From: Robert Hall Date: Fri, 25 Oct 2019 10:13:31 -0600 Subject: [PATCH] Start on potential future css/styles solution --- text/0000-css-in-html.md | 56 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 56 insertions(+) create mode 100644 text/0000-css-in-html.md diff --git a/text/0000-css-in-html.md b/text/0000-css-in-html.md new file mode 100644 index 0000000..a1f3fb0 --- /dev/null +++ b/text/0000-css-in-html.md @@ -0,0 +1,56 @@ +- Start Date: 2019-10-25 +- RFC PR: (leave this empty) +- Svelte Issue: (leave this empty) + +# CSS-in-HTML + +## Summary + +This is a larger RFC focused on solving CSS scoping on both a stand-alone component and global level. This RFC also proposes an approach to reactive CSS as well as better tooling for incorporating 3rd party processors and compilers. + +## Motivation + +> Why are we doing this? What use cases does it support? What is the expected +outcome? + +## Detailed design + +> This is the bulk of the RFC. + +> Explain the design in enough detail for somebody +familiar with the framework to understand, and for somebody familiar with the +implementation to implement. This should get into specifics and corner-cases, +and include examples of how the feature is used. Any new terminology should be +defined here. + +## How we teach this + +> What names and terminology work best for these concepts and why? How is this +idea best presented? As a continuation of existing Svelte patterns, or as a +wholly new one? + +> Would the acceptance of this proposal mean the Svelte guides must be +re-organized or altered? Does it change how Svelte is taught to new users +at any level? + +> How should this feature be introduced and taught to existing Svelte +users? + +## Drawbacks + +> Why should we *not* do this? Please consider the impact on teaching Svelte, +on the integration of this feature with other existing and planned features, +on the impact of the API churn on existing apps, etc. + +> There are tradeoffs to choosing any path, please attempt to identify them here. + +## Alternatives + +> What other designs have been considered? What is the impact of not doing this? + +> This section could also include prior art, that is, how other frameworks in the same domain have solved this problem. + +## Unresolved questions + +> Optional, but suggested for first drafts. What parts of the design are still +TBD? pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy