unfold-nav 0.1.1 → 1.0.0

package/CHANGELOG.md

@@ -1,5 +1,18 @@
 # Changelog
 
+## 1.0.0
+
+The existing navigation, public options, events and styling API become the stable 1.x API.
+
+- Reuse graph geometry and SVG paths during hover and keyboard focus changes; coalesce resize work and read animation timing once per batch.
+- Refresh current-page markers immediately, honor document base URLs, and remeasure labels after resizing, font loading and reopening.
+- Cancel interrupted animation timers and label animations; keep collapsing children out of keyboard and screen-reader navigation.
+- Handle rapid clicks, repeated typeahead letters, held activation keys, input composition and event listeners that close or remove the menu while it opens.
+- Keep user page IDs separate from internal hub and label bookkeeping, including IDs with separator characters.
+- Fall back safely from failing icon callbacks, refresh visible icons when the resolver changes, and copy validated offset objects.
+- Keep inline menus aligned when an ancestor scrolls and let page controls receive pointer input during the closing animation.
+- Add regression coverage for these behaviors while retaining the exhaustive showcase and Circuit layout checks.
+
 ## 0.1.1
 
 - Link the npm homepage and README to the [live showcase](https://unfold-nav.romagnolo.eu).

package/README.md

@@ -13,7 +13,8 @@ same component works with a mouse, a finger or a keyboard, on desktop and on pho
 - **Customisable:** options, `--unfold-*` CSS variables, `::part()` selectors, a slot for the button icon, per-page colours, and a hook to plug in any icon library.
 - **Accessibility features:** a modal dialog with a standard tree of pages for screen readers, full keyboard support, focus management, high-contrast and forced-colors support, text that follows the reader's font size, and reduced motion. See [Accessibility](#accessibility).
 
-This is an early release for compact site maps. The API may change before 1.0.
+Version 1.x keeps the public options, events and styling API stable. It is designed for compact site maps;
+see [layout limits](#layout-limits) and test your real menu content.
 
 ## Quick start
 

package/dist/layout.d.cts

@@ -2,11 +2,11 @@
  * Pure geometry: where nodes go, where their labels go, and how edges are drawn.
  * Coordinates are viewport pixels (y grows downwards, angles are clockwise from +x).
  *
- * The guarantee this file is built around: nothing overlaps. Every node reserves room for its label at
+ * The layout prefers clearance: every node reserves room for its label at
  * the moment its fan is placed, a fan is only accepted when all of its nodes *and* labels fit clear of
  * everything already on screen (nodes, labels, edges, the viewport edge), and later fans have to keep
  * clear of what's reserved. When that's impossible (a tiny screen, a huge menu) labels that don't fit
- * are left out rather than drawn on top of something.
+ * are left out. Extreme density can also exhaust node clearance; see the documented layout limits.
  */
 export interface Vec {
     x: number;

package/dist/layout.d.ts

@@ -2,11 +2,11 @@
  * Pure geometry: where nodes go, where their labels go, and how edges are drawn.
  * Coordinates are viewport pixels (y grows downwards, angles are clockwise from +x).
  *
- * The guarantee this file is built around: nothing overlaps. Every node reserves room for its label at
+ * The layout prefers clearance: every node reserves room for its label at
  * the moment its fan is placed, a fan is only accepted when all of its nodes *and* labels fit clear of
  * everything already on screen (nodes, labels, edges, the viewport edge), and later fans have to keep
  * clear of what's reserved. When that's impossible (a tiny screen, a huge menu) labels that don't fit
- * are left out rather than drawn on top of something.
+ * are left out. Extreme density can also exhaust node clearance; see the documented layout limits.
  */
 export interface Vec {
     x: number;