@panphora/clayjs 1.2.0 → 1.3.0

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 CHANGED
@@ -133,7 +133,10 @@ attribute:
133
133
  ```
134
134
 
135
135
  Tokens: `no-save`, `no-snapshot`, `no-trigger-autosave`, `no-dirty`, `no-watch`, `no-undo`,
136
- `freeze`. Add `autosave` to `<html>` to save automatically on change.
136
+ `no-data`, `editor-ui`, `freeze`. `no-data` excludes a subtree from content-aware reads without
137
+ changing save, watch, snapshot, or undo behavior. `editor-ui` combines `no-data`, `no-save`,
138
+ `no-snapshot`, `no-watch`, and `no-undo` for live editing controls. Native DOM queries still see
139
+ both markers. Add `autosave` to `<html>` to save automatically on change.
137
140
 
138
141
  `no-trigger-autosave` and `no-dirty` are the pair worth getting right. Both are saved in full and
139
142
  neither starts an autosave. The difference is whether their content is *work*: a
@@ -22,6 +22,16 @@ or carry third-party code, and keep their original licenses.
22
22
  - (c) Cure53 and other contributors
23
23
  - https://github.com/cure53/DOMPurify
24
24
 
25
+ ## parse5 7.3.0 (MIT)
26
+
27
+ - File: src/vendor/parse5.vendor.js (the `parse` export only, bundled by
28
+ scripts/build-parse5-vendor.mjs)
29
+ - Used by the `source` plugin, which needs a spec-conformant parse that reports byte
30
+ offsets. No browser exposes one: DOMParser builds the same tree and reports no
31
+ offsets at all.
32
+ - Copyright (c) 2013-2019 Ivan Nikulin and contributors
33
+ - https://github.com/inikulin/parse5
34
+
25
35
  ## Prism 1.29.0 (MIT)
26
36
 
27
37
  - File: website/prism.min.js (core + markup, css, clike, javascript, bash), used