@webqit/oohtml 3.0.1-5 → 3.0.1-7

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.
Files changed (2) hide show
  1. package/README.md +4 -5
  2. package/package.json +1 -1
package/README.md CHANGED
@@ -375,7 +375,7 @@ setTimeout(() => abortController.abort(), 1000);
375
375
 
376
376
  We can defer module loading until we really need them.
377
377
 
378
- Here, we get the `loading="lazy"` directive for that; and loading is only then triggered on the first attempt to import its contents:
378
+ Here, we get the `loading="lazy"` directive for that; and loading is only then triggered on the first attempt to import their contents:
379
379
 
380
380
  ```html
381
381
  <!-- Loading doesn't happen until the first time this is being accessed -->
@@ -900,7 +900,7 @@ Observer.set(element, 'liveProperty'); // Live expressions rerun
900
900
 
901
901
  ## Polyfill
902
902
 
903
- OOHTML is being developed as something to be used today - via a polyfill.
903
+ OOHTML is being developed as something to be used todayvia a polyfill. This is an active and intentional effort that continues to ensure that the project evolves through a practice-driven process.
904
904
 
905
905
  <details><summary>Load from a CDN<br>
906
906
  └───────── <a href="https://bundlephobia.com/result?p=@webqit/oohtml"><img align="right" src="https://img.shields.io/bundlephobia/minzip/@webqit/oohtml?label=&style=flat&colorB=black"></a></summary>
@@ -1040,7 +1040,7 @@ If you'll be going ahead to build a real app to see OOHTML in action, you may wa
1040
1040
 
1041
1041
  ## Examples
1042
1042
 
1043
- Here are a few examples in the wide range of use cases these features cover.
1043
+ Here are a few examples in the wide range of use cases these features cover. While we'll demonstrate the most basic forms of these scenarios, it takes roughly the same principles to build an intricate form and a highly interactive UI.
1044
1044
 
1045
1045
  <details><summary>Example 1: <i>Single Page Application</i><br>
1046
1046
  └───────── </summary>
@@ -1082,7 +1082,7 @@ The following is how something you could call a Single Page Application ([SPA](h
1082
1082
  </template>
1083
1083
  ```
1084
1084
 
1085
- **-->** *Then a 2-line router that alternates the view based on the URL hash*:
1085
+ **-->** *Then a 2-line router that alternates the view based on the URL hash*:
1086
1086
 
1087
1087
  ```html
1088
1088
  <body importscontext="/pages/home">
@@ -1104,7 +1104,6 @@ The following is how something you could call a Single Page Application ([SPA](h
1104
1104
  <details><summary>Example 2: <i>Multi-Level Namespacing</i><br>
1105
1105
  └───────── </summary>
1106
1106
 
1107
-
1108
1107
  The following is a Listbox component lifted directly from the [ARIA Authoring Practices Guide (APG)](https://www.w3.org/WAI/ARIA/apg/patterns/listbox/examples/listbox-grouped/#sc_label) but with IDs effectively "contained" at different levels within the component using the `namespace` attribute.
1109
1108
 
1110
1109
  ```html
package/package.json CHANGED
@@ -14,7 +14,7 @@
14
14
  "wicg-proposal"
15
15
  ],
16
16
  "homepage": "https://webqit.io/tooling/oohtml",
17
- "version": "3.0.1-5",
17
+ "version": "3.0.1-7",
18
18
  "license": "MIT",
19
19
  "repository": {
20
20
  "type": "git",