packages/components/tabs/src/tab-nav.tsx (1)

239-249: ⚠️ Potential issue | 🟠 Major

Add an epsilon when deciding the end state.

Switching to getBoundingClientRect() fixes the integer rounding, but Line 247 and Line 248 still depend on exact equality. If navOffset.value lands at maxOffset - ε, scrollable.value.next stays enabled and the extra-click behavior can still reproduce. Compare the remaining distance against a small pixel epsilon and snap to maxOffset once it falls under that threshold.

Suggested adjustment

       const currentOffset = navOffset.value
+      const edgeEpsilon = 0.5

       if (containerSize < navSize) {
+        const maxOffset = navSize - containerSize
+        const remaining = maxOffset - currentOffset
+        const atEnd = remaining <= edgeEpsilon
         scrollable.value = scrollable.value || {}
         scrollable.value.prev = currentOffset
-        scrollable.value.next = currentOffset + containerSize < navSize
-        if (navSize - currentOffset < containerSize) {
-          navOffset.value = navSize - containerSize
+        scrollable.value.next = !atEnd
+        if (atEnd) {
+          navOffset.value = maxOffset
         }
       } else {

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@packages/components/tabs/src/tab-nav.tsx` around lines 239 - 249, The
end-state check should allow a small pixel epsilon to avoid floating/rounding
issues: compute maxOffset = navSize - containerSize and remaining = maxOffset -
navOffset.value (or remaining = navSize - containerSize - navOffset.value), then
if remaining <= EPSILON (e.g., 1) set navOffset.value = maxOffset and set
scrollable.value.next = false; also use remaining > EPSILON when setting
scrollable.value.next earlier so it disables when within the epsilon. Update the
logic around navSize, containerSize, navOffset, scrollable, nav$, and navScroll$
accordingly.