Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

component selection tool not working #2143

Open
ali2966 opened this issue Mar 2, 2024 · 11 comments
Open

component selection tool not working #2143

ali2966 opened this issue Mar 2, 2024 · 11 comments

Comments

@ali2966
Copy link

ali2966 commented Mar 2, 2024

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

@Parsa361
Copy link

Parsa361 commented Mar 2, 2024

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

@taigabrew
Copy link

taigabrew commented Mar 6, 2024

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

@jiikoosol
Copy link

jiikoosol commented Mar 8, 2024

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

@gregveres
Copy link

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.

@june07
Copy link

june07 commented Mar 19, 2024

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

@idoomguy
Copy link

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

@didaquis
Copy link

I have same problem on macOS using Chrome.

@n4ks
Copy link

n4ks commented Mar 29, 2024

Same problem for a long time

@0x2c9
Copy link

0x2c9 commented Mar 29, 2024

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

@VanillaTank
Copy link

Same problem for a long time, Chrome

@taylordragoo
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests