Last modified: 2014-08-11 19:55:22 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 T71393, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 69393 - Incremental edit summary needed
Incremental edit summary needed
Status: NEW
Product: VisualEditor
Classification: Unclassified
General (Other open bugs)
unspecified
All All
: Unprioritized enhancement
: ---
Assigned To: Editing team bugs – take if you're interested!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-08-11 12:09 UTC by Spinningspark
Modified: 2014-08-11 19:55 UTC (History)
3 users (show)

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


Attachments

Description Spinningspark 2014-08-11 12:09:10 UTC
Intention:
It should be possible to fill out the edit summary incrementally while editing is still taking place, not just in one hit at save time.




Reproducible: Always
Comment 1 WhatamIdoing 2014-08-11 18:24:40 UTC
I believe that what SpinningSpark is actually requesting is to have the edit summary visible and editable on the main screen.  Right now, you can fill out the edit summary incrementally, but you have to click on the Save button and then cancel saving each time.
Comment 2 Spinningspark 2014-08-11 19:55:22 UTC
Actually, I didn't realise you could do that which makes this much less of a problem that I thought it was.  Still, it's a bit clunky. I can't, for instance, start writing the edit summary first (I have to edit something first to make the save button go live).  There are many situations where one has "dirty" data on the clipboard carried from somewhere else and intended for the edit summary.  Have to remember not to copy-paste anything else before dumping it in the edit summary field.

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


Navigation
Links