Today, using the web version of Skritter on mobile, I encountered a bug wherein the app would fail to load the next word after I’d written the current one, starting after I’d gone through a few words.
this.getVocab is undefined. The minification makes it difficult to determine what
this is in this context.
Here is the stack trace (with the full urls shortened to circumvent the link-posting limits):
isCharacterDataLoaded application.js:33 n application.js:1 c libraries.js:46 aa libraries.js:47 l libraries.js:48 Js libraries.js:47 Ao libraries.js:47 h libraries.js:46 Ao libraries.js:47 J libraries.js:46 Ao libraries.js:47 ra libraries.js:47 getNextLoadedUserItems application.js:1 next application.js:43 handlePromptNext application.js:43 i libraries.js:47 f libraries.js:1 M libraries.js:1 p libraries.js:1 trigger libraries.js:1 next application.js:5 handleClickNavigateNext application.js:6 handleClickNavigateNext self-hosted:1003 dispatch libraries.js:37 handle libraries.js:37 i libraries.js:61
The browsers involved are Safari on iOS and Firefox 69.0 on MacOS.