fix(landing): remove cursor lerp causing laggy tracking in collaboration section

[waleedlatif1]

Summary

• Removed the rAF-based lerp (CURSOR_LERP_FACTOR = 0.3) that smoothed the fake YouCursor in the landing page collaboration section — caused visible trail/lag since the native cursor is hidden
• handleMouseMove now sets cursor position directly for 1:1 tracking; dropped the useEffect animation loop and unused refs
• Replaced hardcoded collaboration-heading id with useId() to satisfy biome's useUniqueElementIds rule

Type of Change

• Bug fix

Testing

Tested manually

Checklist

• Code follows project style guidelines
• Self-reviewed my changes
• Tests added/updated and passing
• No new warnings introduced
• I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
docs	Skipped		May 22, 2026 7:33pm

[cursor]

PR Summary

Low Risk
Low risk UI-only change in the landing page that adjusts cursor-follow behavior and accessibility ids, with no backend or data-handling impact.

Overview
Removes the rAF/lerp-based smoothing for the faux YouCursor in the landing page collaboration section and updates mouse handling to set cursor position directly for 1:1 tracking (eliminating visible lag/trailing when the native cursor is hidden).

Updates the section’s aria-labelledby wiring by replacing the hardcoded collaboration-heading id with a useId()-generated id to ensure unique element IDs.

^{Reviewed by Cursor Bugbot for commit d41e0ea. Configure here.}

[gitguardian]

️✅ There are no secrets present in this pull request anymore.

If these secrets were true positive and are still valid, we highly recommend you to revoke them.
While these secrets were previously flagged, we no longer have a reference to the
specific commits where they were detected. Once a secret has been leaked into a git
repository, you should consider it compromised, even if it was deleted immediately.
Find here more information about risks.

---

^{_{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}}

[greptile-apps]

Greptile Summary

Removes the requestAnimationFrame-based lerp (CURSOR_LERP_FACTOR = 0.3) that made the YouCursor trail behind the real pointer, replacing it with direct setCursorPos calls in handleMouseMove. The useId() swap for the heading id satisfies Biome's useUniqueElementIds rule.

• Removed the useEffect animation loop, targetPos ref, and animationRef ref; handleMouseMove now sets cursor state synchronously for 1:1 tracking.
• Replaced the hardcoded \"collaboration-heading\" id with useId() on both the <section aria-labelledby> and <h2 id>, and updated the JSDoc accordingly.

Confidence Score: 5/5

Safe to merge — the change is scoped to a single landing page component and removes animation complexity without altering any data flow or business logic.

The diff removes an rAF loop and two refs, replaces a lerp with a direct state update, and swaps a hardcoded string id for useId(). All three changes are straightforward with no side-effects on the rest of the app.

No files require special attention.

Important Files Changed

Filename	Overview
apps/sim/app/(landing)/components/collaboration/collaboration.tsx	Lerp/rAF animation loop removed; cursor position now set directly in event handlers. useId() replaces hardcoded heading id. No functional regressions introduced.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[Mouse enters section] -->|onMouseEnter| B[setCursorPos + setIsHovering true]
    B --> C[YouCursor renders at viewport coords]
    D[Mouse moves over section] -->|onMouseMove| E[setCursorPos directly]
    E --> C
    F[Mouse leaves section] -->|onMouseLeave| G[setIsHovering false]
    G --> H[YouCursor returns null]

    subgraph Removed
        direction TB
        R1[rAF loop every frame] -->|lerp 0.3| R2[setCursorPos lagging behind]
    end

    style Removed fill:#fef2f2,stroke:#fca5a5

Loading

_{Reviews (3): Last reviewed commit: "fix(landing): remove cursor lerp causing..." | Re-trigger Greptile}

[waleedlatif1]

@greptile-apps Thanks — addressed the P2 JSDoc note in commit ddc2f69. Updated the SEO block to describe the new useId()-generated heading id and clarified that id="collaboration" is the stable URL anchor.

[greptile-apps]

The JSDoc update looks good. The comment now accurately documents both IDs:

• id="collaboration" → stable URL anchor for in-page navigation
• aria-labelledby={headingId} → useId()-generated id linking the <h2> for accessibility

The distinction is clear and the rest of the implementation (direct position tracking, no animation loop) is all in order. LGTM. ✅

[waleedlatif1]

@greptile

[waleedlatif1]

@cursor review

[waleedlatif1]

Reverted the biome --unsafe mass auto-fix commit — it introduced several real bugs (broke StreamWriter.encoder build, merged Tailwind classes in features.tsx and editor.tsx, removed necessary !important in globals.css, SSR-unsafe document? access in text-editor.tsx). PR is back to a single focused commit touching only the landing-page cursor fix. All bot-flagged P1/P2 issues from the prior commit are no longer in the diff.

[waleedlatif1]

@greptile

[waleedlatif1]

@cursor review

[cursor]

✅ Bugbot reviewed your changes and found no new issues!

Comment @cursor review or bugbot run to trigger another review on this PR

^{Reviewed by Cursor Bugbot for commit d41e0ea. Configure here.}