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

Incorrect distance-progress string in context response (sometimes) #420

Closed
terracoda opened this issue Jan 14, 2022 · 6 comments
Closed
Assignees

Comments

@terracoda
Copy link
Contributor

terracoda commented Jan 14, 2022

I haven't isolated when exactly this happens, but it happens, and has been happening from time to time for a while. It is really random and difficult to reproduce, but in the last 5 minutes, I was able to make it happen twice at this url which I believe is the latest version
https://phet.colorado.edu/sims/html/ratio-and-proportion/latest/ratio-and-proportion_en.html

@terracoda
Copy link
Contributor Author

Let's keep this bug in mind as we work on #413 and #419.

@zepumph
Copy link
Member

zepumph commented Jan 20, 2022

I have also seen this before, you move farther away and it says "Closer to . . ." I'll keep my head up for the bug.

@zepumph
Copy link
Member

zepumph commented Jan 21, 2022

I I'm unsure if this is fixed, because I haven't heard the bug in a while, but I feel like it might be from changes in #416 because both hands and single hands description were sometimes overwriting each other's state. I will still be on the lookout for this.

@terracoda
Copy link
Contributor Author

Ok, i will test for this and comment back here.

@zepumph
Copy link
Member

zepumph commented Feb 7, 2022

RE #420 (comment), I'm going to bass this back to @terracoda. #416 and #419 are closed. Please assign back to me if you hear more trouble and can reproduce.

@terracoda
Copy link
Contributor Author

Ok, I think this is fixed, too.
But I am still get a distance-progress string when I hit the challenge when I use the mouse, and when I hit the top.

Is this problem related to this issue, or do we need a new one?
Maybe since this issue is about a bug, we need a new one.

Closing.

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

No branches or pull requests

2 participants