Last modified: 2014-11-13 13:05:11 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 T61004, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 59004 - VisualEditor: Any changes made to an article by other users since switching into VE aren't reflected when switching back to read mode
VisualEditor: Any changes made to an article by other users since switching i...
Status: ASSIGNED
Product: VisualEditor
Classification: Unclassified
MediaWiki integration (Other open bugs)
unspecified
All All
: Low minor
: ---
Assigned To: Editing team bugs – take if you're interested!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-12-27 19:56 UTC by Rummana Yasmeen
Modified: 2014-11-13 13:05 UTC (History)
7 users (show)

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


Attachments

Description Rummana Yasmeen 2013-12-27 19:56:17 UTC
Steps to reproduce:

1.Open an article in read mode in two different tabs of same browser or in two different browsers.

2.Now edit the page using one browser or tab

3.Save the change

4.Now open the same article with VE using another browser or tab

5.Click on "cancel"

Observed Result:
After step 4 the change made in step 2 by another browser or tab are correctly reflected in the edit mode .

But after pressing cancel on step 5 , it has been observed that the readmode is still not showing the change done in step 2 unless user refreshes it.

It will be better if both Edit mode and Read mode shows consistent content even if the change is made by other user/browser session

Test Environment: http://en.wikipedia.beta.wmflabs.org/
Browser: Chrome Version 26.0.1410.65 & FF 25
OS: MAC OS X 10. 8. 5

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


Navigation
Links