Last modified: 2014-10-03 23:20:20 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 T70460, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 68460 - VisualEditor: after dismissing the little pink saving error window, the Save page button remains disabled
VisualEditor: after dismissing the little pink saving error window, the Save ...
Status: RESOLVED INVALID
Product: VisualEditor
Classification: Unclassified
MediaWiki integration (Other open bugs)
unspecified
All All
: Normal normal
: ---
Assigned To: Alex Monk
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-07-23 18:40 UTC by Amir E. Aharoni
Modified: 2014-10-03 23:20 UTC (History)
2 users (show)

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


Attachments

Description Amir E. Aharoni 2014-07-23 18:40:15 UTC
I tried editing a page. I pressed Save and received a little "Something went wrong" window. I pressed "Dismiss". I wanted to try saving again, but the "Save page" button was disabled.

It should probably be re-enabled.

VE Version: 234e4e6, on mediawiki.org.
Comment 1 James Forrester 2014-09-02 14:58:07 UTC
I think we only show the error message for unrecoverable errors. Maybe we should prompt the user to give up rather than just exiting to an unusable save dialog?
Comment 2 Alex Monk 2014-09-02 19:19:34 UTC
ViewPageTarget#showSaveError allows errors to be recoverable or unrecoverable (defaulting to recoverable)

The following errors should be recoverable:
abusefilter
badtoken

The following errors are not:
empty
spamblacklist
unknown

Amir, what error did you run into?
Comment 3 Amir E. Aharoni 2014-09-02 19:21:45 UTC
Hmmmm, don't remember what it could be. Possibly badtoken.
Comment 4 James Forrester 2014-09-02 21:16:06 UTC
Badtoken errors are automatically recovered from, though…
Comment 5 Alex Monk 2014-09-02 22:41:36 UTC
<Krenair> James_F, also, to clarify about badtoken - I was talking about saveErrorNewUser
<Krenair> for invalid session
<Krenair> it appears VE gets a new token to check whether the user ID has changed, when a badtoken error is encountered
<RoanKattouw> Yeah we don't expose a badtoken error to the error handling code unless the API gave us a badtoken error twice
<RoanKattouw> In which case the server's session storage is probably broken
Comment 6 Alex Monk 2014-09-07 21:29:06 UTC
I would mark this invalid until we could find out what error it would've been. But maybe we should make it clear in the UI when an error is unrecoverable (and have related patch(es) point to this bug).

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


Navigation
Links