devtools icon indicating copy to clipboard operation
devtools copied to clipboard

component selection tool not working

Open ali2966 opened this issue 11 months ago • 4 comments

Vue devtools version

6.6.1

Link to minimal reproduction

None

Steps to reproduce & screenshots

click on component selection tool, try to inspect any component, it doesn't work. after closing and opening up the devtools, it will work.

What is expected?

component being selected

What is actually happening?

component not being selected

System Info

System:
    OS: Linux 6.5 Ubuntu 22.04 LTS 22.04 (Jammy Jellyfish)
    CPU: (4) x64 Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz
    Memory: 10.15 GB / 19.41 GB
    Container: Yes
    Shell: 5.1.16 - /bin/bash
  Binaries:
    Node: 14.21.3 - ~/.nvm/versions/node/v14.21.3/bin/node
    npm: 6.14.18 - ~/.nvm/versions/node/v14.21.3/bin/npm
  Browsers:
    Chrome: 115.0.5790.110

Any additional comments?

also, sometimes the devtools freezes and stops working

ali2966 avatar Mar 02 '24 07:03 ali2966

I have the same problem, I wonder why no one mentioned it in these two weeks

Parsa361 avatar Mar 02 '24 08:03 Parsa361

Same problem. Component selection isn't working after hot reload. Personaly saw this with Webpack and Vite. This behaviour started to appear after DevTools major update.

Chrome 122 / MacOS 14.2.1

taigabrew avatar Mar 06 '24 08:03 taigabrew

I have the same problem. Hot reload in some way "freezes" the Vue devtools and requires closing and reopening Chrome's dev-tools, and page refresh after that.

Chrome 122.0.6261.112 / MacOS 14.3.1 / Vite 4.5.2 / Vue 3.4.15

Edit: added Vue version

jiikoosol avatar Mar 08 '24 08:03 jiikoosol

I am seeing the same problem. I have to close the debugger and start the debugger again. I am using vue 2.7 with webpack 4. Oh, I can't wait to be able to move to vue 3 and vite.

gregveres avatar Mar 12 '24 15:03 gregveres

I am seeing the same problem. I have to close the debugger and start the debugger again. I am using vue 2.7 with webpack 4. Oh, I can't wait to be able to move to vue 3 and vite.

Unfortunately, the same persists with Vue 3 and Vite! me: Vue 3.4.21, Vite 5.0.11

june07 avatar Mar 19 '24 17:03 june07

I have exact same problem, after the last major devtools update.

idoomguy avatar Mar 21 '24 15:03 idoomguy

I have same problem on macOS using Chrome.

didaquis avatar Mar 28 '24 14:03 didaquis

Same problem for a long time

n4ks avatar Mar 29 '24 09:03 n4ks

Since the update the devtools are barely usable, every HMR breaks the vue-devtools and only become usable again after the browser devtools are reopened.

In my case Nuxt v3.11.1 / Vue 3.2.21

0x2c9 avatar Mar 29 '24 23:03 0x2c9

Same problem for a long time, Chrome

VanillaTank avatar Apr 03 '24 06:04 VanillaTank

I get the same issue using Chrome and Firefox on macOS. Luckily on Chrome I can right-click and select 'Reload Frame' which reloads the devtools window and the components are updated as expected. As far as I'm aware Firefox does not have the ability to reload the devtool frame and therefore you must close the devtools window and re-open it.

taylordragoo avatar Apr 08 '24 15:04 taylordragoo