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

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

facebook/react 8 comments 1mo ago

mediumopenScope: somewhat clearSkill match: maybeTest focusedReactJavaScriptTypeScript

Why this is a good first issue

Hydration mismatch due to browser-specific attribute requires careful investigation.

AI Summary

The issue involves a hydration mismatch caused by the `__gchrome_uniqueid` attribute in iPad Chrome/Edge browsers, leading to errors in React's hydration process. The problem is reproducible and test-focused, but requires understanding of React's hydration behavior and browser-specific quirks. The scope is somewhat clear but involves browser-specific debugging.

Issue Description

Recreating this issue from https://github.com/vercel/next.js/issues/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

Start development server
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.

GitHub Labels

Status: Unconfirmed

Want to work on this?

Claim this issue to let others know you're working on it. You'll earn 20 points when you complete it!

Risk Flags

browser-specific behavior
hydration issues

Loading labels...

Details

Points20 pts

Difficultymedium

Scopesomewhat clear

Skill Matchmaybe

Test Focusedyes