More about that "text lost when jumping from reading page to 'more options'" bug: huge props to kareila and alierak for figuring out what the entire problem was and writing it all down.
They actually had this bug's number way back in 2015, including a theory for what ended up being the fix; the problem was, web browsers wouldn't allow that fix at the time! Basically, our JavaScript needed to request A Thing (didn't matter what) from the target journal before sending the partial comment over, and cross-domain requests via JS were verboten. But in the time since then, web browsers have added safe ways to do that, so the bug is now fixable without any weird hacks.
Of course, since we're using a contemporary web feature for that, that means the bug is still unfixed for you if you're using a web browser from 2015. *Makes face at IE11.*
no subject
They actually had this bug's number way back in 2015, including a theory for what ended up being the fix; the problem was, web browsers wouldn't allow that fix at the time! Basically, our JavaScript needed to request A Thing (didn't matter what) from the target journal before sending the partial comment over, and cross-domain requests via JS were verboten. But in the time since then, web browsers have added safe ways to do that, so the bug is now fixable without any weird hacks.
Of course, since we're using a contemporary web feature for that, that means the bug is still unfixed for you if you're using a web browser from 2015. *Makes face at IE11.*