Summary

  • On 1 July 2013, the Wikimedia Foundation enabled VisualEditor for all logged-in English Wikipedia users after an opt-in alpha and a test involving half of new accounts. The wikitext editor stayed available.
  • English Wikipedia's default-state discussion closed in favor of an explicit choice to use the beta. On 24 September, a Foundation representative said the default had been disabled and editors could opt in through preferences.

The button arrived before the invitation

For a new contributor, Wikipedia's editing screen could look like a test of punctuation before it became a chance to improve an article. References hid among angle brackets; templates arrived with braces and parameters. The Wikimedia Foundation had a plausible answer: let people edit the page they could see. VisualEditor offered a reference dialog and a visual way to work with templates. It promised to make the first contribution less dependent on fluency in wikitext.

The Foundation's 1 July announcement made that product bet concrete. VisualEditor had spent months as an opt-in alpha on English Wikipedia. A week before the broader rollout, half of newly registered contributors in an A/B test received it automatically. Then every logged-in English Wikipedia user could use it without switching it on in preferences. The source editor remained available. Foundation staff even said VisualEditor lacked some of the functions of raw wikitext. The dispute was therefore about which editor a person met first, not whether source editing survived.

The change also arrived with a work order for volunteers. Help pages had to explain the new interface. TemplateData had to be added to template documentation so visual dialogs could use parameters properly. Other language communities would need translated guidance. The Foundation could ship a button; the communities were asked to build part of the surrounding instruction manual. A default, once set, changes both the visitor's route and the maintenance burden for the people already there.

Editors challenged the default, not the idea

English Wikipedia editors did what people do on a wiki when a disputed change becomes operational: they opened a request for comment. The questions were unusually precise. Should new accounts receive VisualEditor automatically? Should anonymous users see it by default? Should existing accounts have their preferences changed? Should the interface warn that the editor was beta software? The answers in the closure preferred opt-in for new accounts, no default VisualEditor for anonymous editing, and an explicit beta-testing choice for existing editors. A warning about beta status also won support.

That is a sharper story than “editors hated a new tool.” The closer's September summary described strong dissatisfaction with the implementation then in front of users while also noting support for the idea of visual editing, provided direct wikitext editing stayed possible. The concern was the Foundation's decision to make an unfinished interface the ordinary path for other people's work. Beta software is easier to tolerate when the volunteer has chosen to test it; it is harder to defend when a familiar edit button leads into the experiment.

The discussion's own introduction spelled out the institutional problem: the Wikimedia Foundation was not bound by the English Wikipedia consensus. It also noted that Dutch and German Wikipedia communities had persuaded the Foundation to default VisualEditor off. The request for comment could establish the editors' position. It could not by itself reconfigure the production site. The people doing the writing had a voice; the organization deploying the software held the switch.

The switch moved

An editor asked on a MediaWiki feedback page on 24 September why VisualEditor had disappeared from English Wikipedia. Philippe Beaudette, writing for the Foundation, answered that the community's request for comment had asked the Foundation to disable it there and that the Foundation had done so. Registered editors could still create an account and opt in through preferences. That short operational reply is the end of this particular argument: VisualEditor remained a tool; the default stopped recruiting beta testers.

The chronology matters. July's launch was a Foundation decision to expose a new interface broadly. The September RfC was a community decision about the preferred default. The Foundation then made the corresponding software change. Calling the RfC an automatic veto would hand the community authority the record does not show. Calling the Foundation's action mere public relations would miss the changed behavior users actually encountered. One side made a request; the other side moved the setting.

In a public encyclopedia, the edit button is a piece of governance. It decides which skills a newcomer must bring, which errors the experienced volunteer must fix, and whether thousands of habitual editors are suddenly participants in a product trial. The 2013 argument left a useful record of how such decisions can be contested: name the setting, ask who bears the work, record the community answer, and check whether the organization changed the actual route.