Confirmed on Ubiquity 1.5.12. This is almost certainly a result of the changes to ubiquity to have components drive the page turning process. Note that because of this it does not affect incorrect passwords or usernames. The checks on those fields still cause the interface to stay on that page.
Confirmed on Ubiquity 1.5.12. This is almost certainly a result of the changes to ubiquity to have components drive the page turning process. Note that because of this it does not affect incorrect passwords or usernames. The checks on those fields still cause the interface to stay on that page.