@jsenv/navi 0.29.484 → 0.29.485

package/docs/drag_interactions.md

@@ -93,7 +93,10 @@ elsewhere and drops its translate, or it would land twice as far as the hand
 went. A handler that draws nothing (a token on a free canvas) leaves the position
 baked into the element; one whose draw comes later than its answer returns the
 promise of that draw. Something that changes WHILE it is dragged, or must never
-be translated, is [`moving`](#while-it-is-being-moved-moving).
+be translated, is [`moving`](#while-it-is-being-moved-moving). A `transition` on
+`translate` would animate every move of the hand, and the element would trail
+behind it: a carried element transitions anything but `translate` — the way
+back to its place navi animates itself.
 
 **Where it may go.** A `move` stays inside what one can SEE of its scroll
 container — the nearest ancestor whose `overflow` is `auto` or `scroll`, the

package/docs/i18n.md

@@ -231,6 +231,19 @@ look up; the exhaustive list of keys and defaults is the registration block in
 registered by `@jsenv/humanize`. Both go into the one registry `naviI18n` is,
 so overriding either is the same call.
 
+A key whose default holds forms — a message that counts characters, actions,
+line breaks — is overridden with forms too, or the one string is said whatever
+the count:
+
+```js
+naviI18n.add("constraint.min_length.default", {
+  fr: {
+    1: "Au moins [min] caractères (un seul pour l'instant).",
+    other: "Au moins [min] caractères ([count] pour l'instant).",
+  },
+});
+```
+
 **Do not put application texts in `naviI18n`.** Key collisions aside, the two
 have different lifecycles: navi's keys come with the package version, the app's
 come with the app. The unit names it looks up are for rewording a unit navi or

package/package.json

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