John Hunter

Ok. changeOrigin does not do what we might think it does - see https://github.com/chimurai/http-proxy-middleware/pull/141 and https://github.com/http-party/node-http-proxy/pull/1130. There's an argument for http-proxy changing or renaming that setting but since Vite passes...

Seeing this with Chrome 110.0.5481.100, DevTools version: 4.27.2-1a88fbb67

Still happening for me with Chrome Version 111.0.5563.146, extension Version 4.27.3 This is on localhost. The following workaround is less than ideal but gets me out of a bind: -...

> Remove the extension and install it again. This did not resolve the problem. Still happening with fresh install of extension 4.27.8 and Chrome 114.0.5735.133

@hoxyq can we reopen this issue please. It does not appear to be resolved and the behaviour is different from #25818 - thanks.

> I need more information about the problem Thanks. I see a lot of `TimeoutError: Timed out while inspecting element nnn` errors once I undock the panel. But so far...

When the stuck condition occurs; undocking the panel and opening the console shows the following: Closing and reopening the DevTools panel seems to reset the tree. This is different to...

Yep, that was the console in the screenshot. Here is the issue reproduced again. In this case the error log did not appear until I selected another DevTools panel tab...

I'm still seeing this issue, even on fairly small projects. react: 18.2.0 react-dom: 18.2.0 react-devtools: 4.28.0 os: MacOS 13.5.2

@hoxyq Thanks, I'll report back when I get a chance to verify.