packages/virtual-core/src/index.ts (1)

742-756: 💤 Low value

Consider edge case: scrollOffset is null when force-flushing.

In _forceFlushIosDeviation, if scrollOffset is null and _iosDeferredAdjustment is non-zero, rawBrowserScroll would compute as a negative value (0 - adjustment). While this scenario is unlikely in practice (deviation is only accumulated after scroll events set scrollOffset), a defensive guard would prevent unexpected behavior if the invariant is violated.

🛡️ Optional defensive guard

 private _forceFlushIosDeviation = () => {
   if (this._iosDeferredAdjustment === 0) return
+  if (this.scrollOffset === null) {
+    // No scroll offset yet; just clear the deviation state
+    this._iosDeferredAdjustment = 0
+    this._applyIosDeviation()
+    return
+  }
   const rawBrowserScroll =
     (this.scrollOffset ?? 0) - this._iosDeferredAdjustment

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@packages/virtual-core/src/index.ts` around lines 742 - 756, If
this._iosDeferredAdjustment is non-zero but this.scrollOffset is null, computing
rawBrowserScroll yields an incorrect value; add a defensive guard at the top of
_forceFlushIosDeviation to handle null scrollOffset (e.g. if this.scrollOffset
== null then clear _iosDeferredAdjustment and call _applyIosDeviation and
return) so you don't call _scrollToOffset with an invalid rawBrowserScroll;
reference the method name _forceFlushIosDeviation and the fields scrollOffset,
_iosDeferredAdjustment and the helpers _applyIosDeviation and _scrollToOffset
when making the change.

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes