Topic on 2017 wikitext editor/Feedback

Feature: VisualEditor's text editing mode intentionally does not encourage null edits

13
Brainulator9 (talkcontribs)

The current version does not allow null edits. Is this intentional? Thank you.

Jdforrester (WMF) (talkcontribs)

Yes, "null edits" shouldn't ever be needed.

Brainulator9 (talkcontribs)
IKhitron (talkcontribs)

We use'em all the time.

Jdforrester (WMF) (talkcontribs)

The instruction from the Performance team is to file a bug if you find a situation where you think you need a null edit.

Alsee (talkcontribs)

Yes Done title changed to officially list this as a bug report on the official 2017 wikitext editor/Feedback page.

Brainulator9 (talkcontribs)

I wasn't necessarily reporting it as a bug, though, just asking to clarify if that was an intentional design choice.

IKhitron (talkcontribs)

You are kidding?

Alsee (talkcontribs)

@IKhitron, I could be mistaken, but I believe JDF is the one primarily responsible for accepting/rejecting issues in this area. For example the lack of a directly accessible preview button, dysfunctional CTRL-V paste paste behavior, faulty previews, etc etc etc.

IKhitron (talkcontribs)

Absolutely. I'm talking about null edits.

Whatamidoing (WMF) (talkcontribs)

You can make a null edit in the 2017WTE:

  1. Open the page
  2. Make any change (e.g., type one space).
  3. Undo that change (must be done exactly).
  4. Click the big blue button.
  5. Don't add an edit summary.
  6. Click the big blue button.
  7. (Optional: Get a warning that you didn't add an edit summary, and click the big blue button again.)

In the older wikitext editors, steps 2 and 3 would not be needed.

Alternatively, you can hand-edit the URL to change &veaction=editsource or equivalent to &action=submit and drop into an older wikitext editor to do this.

Reply to "Feature: VisualEditor's text editing mode intentionally does not encourage null edits"