You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@julien4215 i may struggle to give proper repro steps but gonna give it a try
It's happened ever since it was added but here's a good point in a specific game where I can repro a good amount
https://lichess.org/69Tv4C4U
If you hold anywhere on the chart where the line currently is not so it activates ability to drag it and then drag right near the y-axis by "end game" if you do it 5-6 times in a row you should be able to reproduce at least once or twice. When dropping it on that y-axis exactly it'll often bounce one spot over.
Happy to answer any follow up questions for further clarification but I don't believe a video will help show off the issue
The text was updated successfully, but these errors were encountered:
Glad you could reproduce, was fearful it'd be harder to articulate it
To Be honest I wish the tab switch was slightly less sensitive. All the time when I'm scrolling analysis and such I switch tabs when I don't even want to
And when the tabs were added, the simplest way to drag the chart was removed (now you have to hold down in a new sport first but before you could kinda go with it much easier right when you put your finger down)
@julien4215 i may struggle to give proper repro steps but gonna give it a try
It's happened ever since it was added but here's a good point in a specific game where I can repro a good amount
https://lichess.org/69Tv4C4U
If you hold anywhere on the chart where the line currently is not so it activates ability to drag it and then drag right near the y-axis by "end game" if you do it 5-6 times in a row you should be able to reproduce at least once or twice. When dropping it on that y-axis exactly it'll often bounce one spot over.
Happy to answer any follow up questions for further clarification but I don't believe a video will help show off the issue
The text was updated successfully, but these errors were encountered: