Retrospectively collapse subsequent rapid edits into a single revision ("edit your edit")
Open, LowestPublicFeature
Actions

Assigned To

None

Authored By

	Svick
	Jun 24 2013, 10:11 PM

Description

On Stack Overflow, when you edit a post within 5 minutes of your last edit and nobody edited the post in the meantime, the edits are merged into one. This way, if you find a mistake in your edit, or if you quickly find something else to change after the edit, only one edit will be visible.

I think having full revision history is much more important in MediaWiki than on SO, but something like this could be useful anyway. Maybe something like keeping the default the same, but adding an option to edit the last edit could make sense.

(I would be surprised if a feature like this wasn't suggested before, but I didn't find it here.)

Version: 1.22.0
Severity: enhancement

Details

Reference: bz50137

Event Timeline

• bzimport raised the priority of this task from to Lowest.Nov 22 2014, 2:01 AM

• bzimport added a project: MediaWiki-Page-editing.

• bzimport set Reference to bz50137.

• bzimport added a subscriber: Unknown Object (MLST).

Svick created this task.Jun 24 2013, 10:11 PM

I'm not sure how this is supposed to work for MediaWiki - 5 min are already a really long time and bots etc. would revert potential vandalism in way less than 5 min. StackOverflow likely has way less 'heated' changes and fast edits.

Ltrlg subscribed.Jan 17 2015, 11:41 PM

This is possible on flow, but for actual wiki pages suggest declining

Jdforrester-WMF renamed this task from Editing edits to Retrospectively collapse subsequent rapid edits into a single revision ("edit your edit").Nov 22 2019, 7:37 PM

Jdforrester-WMF removed a subscriber: • wikibugs-l-list.

I've re-titled this to be clearer what it's suggesting.

In T52137#5685373, @DannyS712 wrote:

This is possible on flow, but for actual wiki pages

No, it isn't.

suggest declining

Perhaps. It's hard to see how we'd change the immutability concept of revisions, but I can see the value. Possibly a new, "virtual" revision could be added instead and history slightly re-written, which wouldn't break immutability (we'd re-write the revision table a little but not the text / external store)? It's an interesting product use-case.

Aklapper changed the subtype of this task from "Task" to "Feature Request".Feb 4 2022, 11:14 AM

Retrospectively collapse subsequent rapid edits into a single revision ("edit your edit")Open, LowestPublicFeatureActions

Description

Details

Event Timeline

Retrospectively collapse subsequent rapid edits into a single revision ("edit your edit")
Open, LowestPublicFeature
Actions