@surstromming/dropdown-menu 0.1.1 → 0.1.2

package/CHANGELOG.md

@@ -1,5 +1,20 @@
 # @surstromming/dropdown-menu
 
+## 0.1.2 — 2026-07-26
+
+### Fixed
+
+- **Closing a menu no longer scrolls its trigger back into view.** Focus still
+  returns to the trigger, but with `preventScroll` now. What usually closes a
+  menu is a press somewhere else, and the return runs before that press has
+  focused what it hit — so in a long list, opening a menu on the first row,
+  scrolling well past it and pressing another row's trigger yanked the page
+  back to the first row. The press places focus itself a moment later, so only
+  the scroll is given up; Escape and selecting an item are unchanged, and a
+  trigger reached by keyboard is on screen to begin with.
+
+  No API change.
+
 ## 0.1.1 — 2026-07-26
 
 ### Fixed

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@surstromming/dropdown-menu",
-  "version": "0.1.1",
+  "version": "0.1.2",
   "description": "A menu of actions anchored to a trigger.",
   "license": "MIT",
   "author": "Evgeniy Mnatsakanov <evgeniy.mnatsakanov@gmail.com>",

package/src/DropdownMenu.vue

@@ -123,7 +123,12 @@ watch(open, async (isOpen) => {
     await nextTick()
     focusEdge('start')
   } else if (menu.value?.contains(document.activeElement)) {
-    trigger?.focus()
+    // `preventScroll`, because what usually closes a menu is a press somewhere
+    // else, and this runs before that press has focused what it hit. Scrolling
+    // the trigger back into view drags the page to wherever its row happens to
+    // be — in a long list, nowhere near what the reader is looking at. The
+    // press then puts focus where it belongs, so only the scroll is given up.
+    trigger?.focus({ preventScroll: true })
   }
 })