Bug: Hydration issue involving __gchrome_uniqueid on iPad Chrome/Edge browser

[danvim]

Recreating this issue from vercel/next.js#77710 as Next team mentioned this relates more to React's hydration behavior.

React version: 19.1.0
iPad Chrome: 135.0.7049.53
iPad Edge: 134.3124.95
iPad Safari tested without issues.

Steps To Reproduce

See reproduction

1. Start development server
2. Visit development server via iPad Chrome/Edge browser app.

Link to code example: https://github.com/danvim/next-gchrome-hydration-reproduction

The current behavior

Hydration failed because the server rendered HTML didn't match the client...

    <Home>
      <input
-      __gchrome_uniqueid="1"
      >
    ...

The expected behavior

Expected no error.

[Preeti1799]

Hi! 👋 I'd love to take a look into this issue. I'll try to reproduce the bug and investigate further.