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

Multivec track shows horizontal crosshair when mouse pointer is not over multivec track #814

Open
alexpreynolds opened this issue Dec 16, 2019 · 2 comments · May be fixed by #1072
Open

Comments

@alexpreynolds
Copy link
Collaborator

Using v1.7.2 of higlass, I have a horizontal-multivec track along with a few other non-multivec tracks (gene annotations, horizontal-point, and chromosome tracks).

When the mouse pointer moves over a non-multivec track, the multivec track behaves as though the vertical coordinate of the mouse pointer is also on the multivec track, which enables the horizontal line of the crosshair:

Crosshair

What I would expect is that, when the multivec is part of the top or bottom of a view, it would only show the horizontal crosshair if the pointer is within the bounds of the multivec track.

(Likewise, if the bug is consistent between orientations, a multivec that is in the left or right portion of a view would not show the vertical crosshair, unless the pointer is within the bounds of the multivec.)

@keller-mark
Copy link
Member

Hi, are you still experiencing this bug? I tried to reproduce it here http://higlass.io/app/?config=TuwAlswBRLSkikCjBlbZhw but do not see the behavior you experienced in firefox or chrome.

@alexpreynolds
Copy link
Collaborator Author

alexpreynolds commented Jan 30, 2020

Yes, but I haven't been able to update my local copy of the higlass plugin due to local changes (unrelated to the multivec track). There may have been fixes applied to the higlass.io site since I reported this bug.

alexpreynolds added a commit that referenced this issue Dec 1, 2021
When the `showMousePosition` option is set to `true` and the mouse pointer moves over a non-2d track, x and y values are published internally that can cause another 2d track to draw nonsensical vertical or horizontal lines. This test clears the relevant value so that it cannot be used to render such lines.
@alexpreynolds alexpreynolds linked a pull request Dec 1, 2021 that will close this issue
7 tasks
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

Successfully merging a pull request may close this issue.

2 participants