Last modified: 2013-08-25 10:35:54 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T55314, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 53314 - VisualEditor: inconsistency when reviewing changes after a null edit
VisualEditor: inconsistency when reviewing changes after a null edit
Status: RESOLVED DUPLICATE of bug 53313
Product: VisualEditor
Classification: Unclassified
General (Other open bugs)
unspecified
All All
: Unprioritized normal
: ---
Assigned To: James Forrester
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-08-25 10:32 UTC by Elitre
Modified: 2013-08-25 10:35 UTC (History)
2 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Elitre 2013-08-25 10:32:26 UTC
User report:
<<So I put a space and then a backspace.  Go to save, review changes to check and make sure it is a null edit, then it goes to this "processing" dialogue but then it shows "Could not start the review because your revision matches the latest version of this page."  So then I press the little back link on the dialogue, but it just goes back to the processing dialogue.  If the page is small, the processing is really quick, so before I can even press back again, it goes back to the "Could not start" warning message.  Even if I do manage to press the back a second time quickly, it will only stay at the save dialogue for a split second and then again bring me to the warning message, although ''then'' pressing back does take me to the save dialogue securely.  FF 23.0.1 Win7.>>

I managed to reproduce this on Chrome as well, so which is the intended left button behaviour?
Thanks.
Comment 1 Elitre 2013-08-25 10:35:54 UTC

*** This bug has been marked as a duplicate of bug 53313 ***

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links