I went to the “Lessons Summary” page (/lesson) and started a session. Then I clicked the back button. Rather than showing the “Lessons Summary” page again, it showed the API data that is usually displayed on that page. For example, the second time I tried this (when the summary was empty) it displayed {"radicals":[],"kanji":[],"vocabulary":[],"queue_count":63,"last_lesson_date":"2017-07-09T23:43:39.666Z"}.
What browser/version/OS are you on? The back button having that behavior is pretty strange — I reviewed the flow through the app, and the browser never hits/gets redirected through the API.
This just happened to me too. On Chrome. Clicked on an item after lessons to view details and then when I clicked back got something like in the OP but about fifty times as long. When I clicked back again it took me straight into a set of new lessons.
This happened to me about 2 hours ago on Firefox. Windows 7.
Did a session of around 35-37 reviews, and hitting back from either 具合 or 場合 I had a long page full of the JSON code. Colour-coded, as if I had the console open.
Clicking Refresh made the review summary page appear normally. (I had taken a screenshot of it to post in the WK screenshots thread as a joke, while also remembering this thread… but then wound up posting a lot of other things and copied something over it in the clipboard. Oops.)
It’s probably because they’re using the same endpoints for HTML and JSON requests. If the site has done an AJAX request to that endpoint since you last visited the page that’s what your browser has cached so that’s what it shows when you click back.
This happens to me too, I honestly thought it was intended since it’s so consistent. Chrome on Windows 10. It doesn’t bother me since the only time I back out of lessons or reviews like that is on accident.
I had gone to the radical “glue” to give it the synonyms つ, tsu, and attach. Since I already know it that way. When I clicked back in the browser, that was the result.
It has to do with how some browsers handle responses for different formats at the same URL — in our case, we’ve got /reviews and /lessons set to respond to HTML and with JSON. The browser gets a bit confused about which response show up when you hit back, and it’s showing the JSON response. One would think it would be the page the user navigated to, but, well, browsers…
We’ve got a plan to clear it up, but it’ll take a couple days to knock out the fix. I’ll let everyone know when it’s live, although you’ll probably be able to tell, as the bug won’t happen anymore.
Yep, we’re still working on the fix — a few other things got put higher on the priority list, so it’ll be a little while (like, the week of the 21st) before we wrap this one up.
