Add Troubleshooting Section to react-developer-tools.md

[fkellner]

trafficstars

Taken from https://github.com/facebook/react/issues/27338, these are the helpful points which helped me resolve my issue (old version of Chrome) and which I would have expected to be part of the documentation.

[vercel[bot]]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
react-dev	✅ Ready (Inspect)	Visit Preview	Feb 21, 2024 0:57am

[facebook-github-bot]

Hi @fkellner!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at [email protected]. Thanks!

[github-actions[bot]]

Size changes

📦 Next.js Bundle Analysis for react-dev

This analysis was generated by the Next.js Bundle Analysis action. 🤖

This PR introduced no changes to the JavaScript bundle! 🙌

[fkellner]

Why would I need to have a CLA for this? Does this not entirely defeat the point of proposing changes with a low barrier of entry? I literally copy-pasted an Answer from a Github issue, so I cannot even say those changes are mine...

[facebook-github-bot]

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks!