@jsenv/navi 0.30.36 → 0.30.38

package/docs/resource.md

@@ -536,6 +536,10 @@ const ORDER = resource("order", {
 <Button action={ORDER.cancel.bindParams({ id })}>Cancel</Button>;
 ```
 
+A write's name is its own: never a verb's, in any case (`post`, `Patch`,
+`get_many`…), nor a member the resource already exposes (`store`, `one`,
+`scopedMany`, `withParams`…). Declaring the resource throws otherwise.
+
 `ORDER.cancel` is an action beside the verbs: its own loading and error on the
 button that runs it, held by the network policy as its `verb`, and answered as
 that verb is (a `PATCH` returns the item, which is upserted). Its `rerunOn` says

package/docs/scroll.md

@@ -756,6 +756,12 @@ browser, at no cost per element. Hand-written in JS the same suppression takes
 three handlers — once `mouseenter` has been swallowed, only `mousemove` can
 bring the hover back.
 
+End the selector on what it styles, as `.my_row` does here. A rule ending on
+`*` (`[navi-scrolling] *`, or `.my_row:is([navi-scrolling] *)`) gives Chrome
+nothing to narrow to: it restyles every element under the scroller, the whole
+document when the page scrolls, once as each scroll starts and again as it
+stops.
+
 The page scroll carries the attribute on `document.scrollingElement`, so an
 ancestor rule covers it too. In JS the same fact reads as `isScrolling()` /
 `isScrolling(element)`, or `scrollActivitySignal` to react to it.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@jsenv/navi",
-  "version": "0.30.36",
+  "version": "0.30.38",
   "type": "module",
   "description": "Library of components including navigation to create frontend applications",
   "repository": {