@webqit/oohtml 2.1.39 → 2.1.40
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +4 -6
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -12,9 +12,6 @@ Object-Oriented HTML (OOHTML) is a set of language features for authoring modula
|
|
|
12
12
|
|
|
13
13
|
OOHTML is an upcoming proposal!
|
|
14
14
|
|
|
15
|
-
> **Warning**
|
|
16
|
-
> <br>The syntax on this page isn't finalized. You may need to keep tabs with us.
|
|
17
|
-
|
|
18
15
|
## Motivation
|
|
19
16
|
|
|
20
17
|
The web has generally outgrown HTML's idea of a monolith architecture which has held to the document as the unit of abstraction for scripts, style sheets, and element identifiers (the `id` attribute, and in some scenarios, the `name` attribute). You realize that while you're trying to *model things* in markup and are thinking in objects, components, logical building blocks, reusable units of abstraction - as we have of things like [Vue's SFC](https://vuejs.org/api/sfc-spec.html), [Svelte component format](https://svelte.dev/docs#component-format-script), [11ty's WebC](https://www.11ty.dev/docs/languages/webc/#css-and-js-(bundler-mode)) - the language for the job is posing a "per document" constraint!
|
|
@@ -744,7 +741,7 @@ Also, if you'll be going ahead to build a real world app to see OOHTML in action
|
|
|
744
741
|
</details>
|
|
745
742
|
|
|
746
743
|
<details><summary>
|
|
747
|
-
|
|
744
|
+
Implementation Notes
|
|
748
745
|
</summary>
|
|
749
746
|
|
|
750
747
|
Here are the performance-specific notes for this polyfill:
|
|
@@ -771,8 +768,7 @@ Here are the performance-specific notes for this polyfill:
|
|
|
771
768
|
|
|
772
769
|
Here are other notes:
|
|
773
770
|
|
|
774
|
-
+ **Scoped CSS**. This feature is only in "concept" implementation and doesn't work right now as is. The current implementation simply wraps `<style scoped>` blocks in an `@scope {}` block - which itself isn't supported in any browser.
|
|
775
|
-
Public](https://github.com/samthor/scoped). To try the "concept" implementation, set the `style.strategy` config to `@scope`:
|
|
771
|
+
+ **Scoped CSS**. This feature is only in "concept" implementation and doesn't work right now as is. The current implementation simply wraps `<style scoped>` blocks in an `@scope {}` block - which itself isn't supported in any browser. To try this "concept" implementation, set the `style.strategy` config to `@scope`:
|
|
776
772
|
|
|
777
773
|
```html
|
|
778
774
|
<head>
|
|
@@ -799,6 +795,8 @@ Public](https://github.com/samthor/scoped). To try the "concept" implementation,
|
|
|
799
795
|
</style>
|
|
800
796
|
```
|
|
801
797
|
|
|
798
|
+
A working implementation may be coming soon, but in the meantime, you could try one of the polyfills for `<style scoped>` out there; e.g. [samthor/scoped](https://github.com/samthor/scoped).
|
|
799
|
+
|
|
802
800
|
+ **HTML Imports**. The attribute names for exposing reusable modules and for referencing them - the `def` and `ref` keywords, respectively - aren't finalized. While the principle of operation remains, these attributes may be renamed in subsequent iterations. But the polyfill is designed to always defer to any syntax that has been explicitly specified using a meta tag. Here's an example:
|
|
803
801
|
|
|
804
802
|
```html
|