Page MenuHomePhabricator

VisualEditor: After "wikimarkup" popup, save button temporarily does not work
Closed, ResolvedPublic

Description

An editor reports that he lost his work when an extensive edit unexpectedly triggered the "wikimarkup" popup and - after he dismissed it - the "save" button became unresponsive. The button appeared as normal but did not react to being selected.

He was using Windows 7 and Firefox.

I reproduced this using Windows 7 and Chrome (didn't matter if I removed the wikimarkup or not), and on further investigation found that the "save" button will respond as expected after a delay.

The issue, of course, is that if this editor aborted his edit because he thought the system would not save, others are likely to think that as well.

Not sure if anything can be done to make the save button immediately responsive or to figure out why it wouldn't be or to make it apparent to editors that the option to "save" will return.

The conversation can be found here:
http://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=567809017#Wikitext_error_message


Version: unspecified
Severity: normal

Details

Reference
bz52669

Event Timeline

bzimport raised the priority of this task from to Needs Triage.Nov 22 2014, 2:01 AM
bzimport added a project: VisualEditor.
bzimport set Reference to bz52669.

en.wp user GermanJoe reports a probably related problem:

After dismissing the wikitext warning the "upper third and right corner" of the save and cancel buttons are not clickable." and that "Those partial locks are only released, after you clear your browser cache (stopping VE is not enough) "

GermanJoe was using Windows XP, FF 22, vector.js and a 1280 x 1024 resolution for test. He did not experience the problem in 800x600 resolution.

Elitre was able to reproduce this and added that "this behavior changes if you zoom in or out (that is, if the buttons get bigger or smaller)"

I reproduce this using Monobook in Firefox 23 on Linux, but zooming the page did not result in changed behaviour for me.

Is this still occurring? I think we've fixed it, so am marking as FIXED, but would prefer to get confirmation.