Hi!
I enjoy doing the "Learn" puzzles. I would occasionally see a bug where it presents the same problem again after you just solved it. This bug has been in the system since I've been playing here, and that's awhile. :)
Your choices here would be to do it again, and get "plus zero" points for the repeat. I found a workaround for that, which was to click the rightmost arrow, essentially fast-forwarding to the end of the problem. When doing this, I didn't have to solve the problem again, and as expected, I also got the "plus zero". Still buggy, but not too bad. I didn't bother complaining before, because I know you folks are pretty busy, and this didn't ding me for points or happen that often.
As of today, the rightmost arrow approach stopped working, and it deducts points. :) I'm guessing that some well-intentioned person was trying to solve another bug, but actually ended up making things worse. I don't want to solve the problem again each time this happens. Could somebody take a look at this?
In case it's useful info, I'm using the latest Chrome browser on Windows. When I use the phone app I don't recall running into this problem.
Thanks.
I enjoy doing the "Learn" puzzles. I would occasionally see a bug where it presents the same problem again after you just solved it. This bug has been in the system since I've been playing here, and that's awhile. :)
Your choices here would be to do it again, and get "plus zero" points for the repeat. I found a workaround for that, which was to click the rightmost arrow, essentially fast-forwarding to the end of the problem. When doing this, I didn't have to solve the problem again, and as expected, I also got the "plus zero". Still buggy, but not too bad. I didn't bother complaining before, because I know you folks are pretty busy, and this didn't ding me for points or happen that often.
As of today, the rightmost arrow approach stopped working, and it deducts points. :) I'm guessing that some well-intentioned person was trying to solve another bug, but actually ended up making things worse. I don't want to solve the problem again each time this happens. Could somebody take a look at this?
In case it's useful info, I'm using the latest Chrome browser on Windows. When I use the phone app I don't recall running into this problem.
Thanks.