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

Inspector does not select the lowest element when you move the mouse. It only selects the ancestor of the lowest element. #448

Closed
lukaszpolowczyk opened this issue Sep 22, 2022 · 0 comments · Fixed by #449
Labels
bug Something isn't working

Comments

@lukaszpolowczyk
Copy link

Describe the bug

Before that, I didn't know what was going on, what the problem was.

Inspector does not select the lowest element, after moving the mouse. It only selects the ancestor of the lowest element.
Turning it off and on (without moving the mouse), allows you to select the lowest element.

Reproduction

  1. hover over an element
  2. press toggleKeyCombo to enable the inspector
  3. inspector selects the indicated element correctly
  4. move the mouse cursor outside the selected element
  5. move the mouse cursor back to the previously selected element

Effect: previously selected element, does not want to select.

It is impossible to select it, without using Nav child.

Pressing toggleKeyCombo twice, fixes, the indicated element is selected again (as long as you do not move the mouse cursor).

When you move the mouse cursor, you can never select the element, only the ancestor of the element, which without moving the mouse cursor, you could select.

Logs

No response

System Info

System:
    OS: Linux 5.10 Arch Linux
    CPU: (4) x64 AMD Athlon(tm) X4 950 Quad Core Processor
    Memory: 8.79 GB / 15.07 GB
    Container: Yes
    Shell: 5.1.8 - /bin/bash
  Binaries:
    Node: 18.4.0 - ~/.nvm/versions/node/v18.4.0/bin/node
    Yarn: 1.22.10 - /usr/bin/yarn
    npm: 8.12.1 - ~/.nvm/versions/node/v18.4.0/bin/npm
  Browsers:
    Brave Browser: 100.1.37.109
    Firefox: 102.3.0esr
  npmPackages:
    @sveltejs/adapter-auto: next => 1.0.0-next.76 
    @sveltejs/kit: next => 1.0.0-next.490 
    svelte: ^3.44.0 => 3.50.1 
    vite: ^3.1.0-beta.1 => 3.1.3

Severity

annoyance

@lukaszpolowczyk lukaszpolowczyk added bug Something isn't working triage Awaiting triage by a project member labels Sep 22, 2022
@dominikg dominikg removed the triage Awaiting triage by a project member label Sep 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants