[react dev tools] errors + unresponsive to clicks

[roy-s]

1. There are ofter errors relating to the addition of nodes to the store. Could this failure be more silent, and not completely hide the display?

2. When opening the react dev tools in a separate window, it does not respond to clicks or hover in the tree section. I can still click a component in the "rendered by" section. Note that this does not happen when the dev tools are opened in the same window. Update: it also didn't happen when I tried to put the two windows side by side in the same screen for a recording...

Please see the attached screen capture for both issues.

rect_dev_tool_issues.mov

Thanks

[leidegre]

I noticed this today to. At first I thought it was due to high cpu usage or some infinite loop stuff but it happens as soon as you try to scroll the tree view. This makes it difficult to navigate up in the component tree.

Using this version of React DevTools 4.24.6-ca7a38ae4

(not sure if this matters but...) I'm on React 16.13.1 and the issue is consistent between dev and prod builds.

[hinok]

Confirm. The same issue with 16.9.0 but splitting window doesn't have any impact.
In my case opening dev tools and trying to click on anything inside the left Components window - "does nothing".
I'm able to fold/unfold items using a keyboard.

[Mathias-S]

Can confirm. When inspecting the devtools itself, I noticed that the div that lists the elements gets pointer-events:none when you start scrolling in it. When I remove that, it starts working as expected again.

• React 17.0.2
• Devtools version 4.24.6-ca7a38ae4
• Chrome 102.0.5005.61

Edit: This is a duplicate of #24626

[petermarkovich]

Confirm. After "Seelct element to inspect", sometimes clicking on the component tree does not working. Only restart chrome dev tools help me.
Chrome: 102.0.5005.63
React: 16.9.0
React dev tools: 4.24.6 (5/12/2022)
it refers to №24626

[lunaruan]

This is a duplicate of #24626. It's a Chrome bug in v102. We're working on a fix but for a temporary workaround:

1. go to chrome://flags/
2. search for Throttle non-visible cross-origin iframes
3. change the flag to disable
4. relaunch Chrome to make the change effective