Not sure - but it would be nice if the errors were "somehow" displayed at your current location in the page
Actual Behavior
If you're on a long pensieve, and you've scrolled halfway down the page, and an error occurs, the error is only displayed at the very top of the page, which means that a) you can't tell that an error has occurred b) you have to scroll all the way up to the top of the page if you guess that an error has occurred and you want to see what the error says c) you then have to scroll back down again to try and find where you were before you scrolled up to read the error, which can be very inconvenient
Steps to Reproduce the Problem
The easiest way to trigger an error seems to be to make lots of rapid edits, which triggers the "Conflict" error (see #190 )
Expected Behavior
Not sure - but it would be nice if the errors were "somehow" displayed at your current location in the page
Actual Behavior
If you're on a long pensieve, and you've scrolled halfway down the page, and an error occurs, the error is only displayed at the very top of the page, which means that a) you can't tell that an error has occurred b) you have to scroll all the way up to the top of the page if you guess that an error has occurred and you want to see what the error says c) you then have to scroll back down again to try and find where you were before you scrolled up to read the error, which can be very inconvenient
Steps to Reproduce the Problem
The easiest way to trigger an error seems to be to make lots of rapid edits, which triggers the "Conflict" error (see #190 )
Specifications
whatsmybrowser.org/b/MDKAR48