Last modified: 2014-03-01 00:13:08 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 T59314, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 57314 - VisualEditor:Cannot save the content of a page after an idle time on the open editor
VisualEditor:Cannot save the content of a page after an idle time on the open...
Status: NEW
Product: VisualEditor
Classification: Unclassified
Editing Tools (Other open bugs)
unspecified
All All
: Unprioritized normal
: ---
Assigned To: Editing team bugs – take if you're interested!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-11-20 18:03 UTC by Rummana Yasmeen
Modified: 2014-03-01 00:13 UTC (History)
7 users (show)

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


Attachments

Description Rummana Yasmeen 2013-11-20 18:03:05 UTC
Steps to reproduce:

1.Open the VE editor for a page.
2.Make some edit
3.Leave the editor open for a long time (more than an hour)
4.Come back after that idle time and click the button "Save Page"


Observed Result:
The content does not get saved.Shows a js error in the console

Uncaught TypeError: Cannot read property 'saveRetries' of undefined
(anonymous function)
fire load.php:12
self.fireWith load.php:14
self.fire load.php:14
(anonymous function)
fire load.php:12
self.fireWith load.php:14
done load.php:119
callback
Comment 1 Rummana Yasmeen 2013-11-20 18:04:00 UTC
Test Environment: production
Browser: Chrome Version 26.0.1410.65 & FF 25
OS: MAC OS X 10. 8. 5 
Example Page:https://en.wikipedia.org/wiki/User:RYasmeen_%28WMF%29/test_reference
Comment 2 Elitre 2013-11-25 17:55:39 UTC
I am curious about how different this is from the common behavior with the wikitext editor, which will usually display a message like "Sorry! We could not process your edit due to a loss of session data. Please try again. If it still doesn't work, try logging out and logging back in." (not sure if this is the actual one though) and which "fixes" itself if you just retry to save.

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


Navigation
Links