Page MenuHomePhabricator

Flow must have editing mode setting
Open, Needs TriagePublic

Description

If you almost exclusively use wikitext, but sometimes make minor fixes (e.g. typos) in VE while previewing, you may not start in the desired mode next time.


Original description:

"Remember last mode" is awful. In fact it is so awful that it has nearly 100% error rate for the majority of users.

VE statistics show that the overwhelming majority of editors use wikitext exclusively or primarily. Lets examine the flowchart for wikitext editors:

  1. edit in wikitext mode
  2. click to preview
  3. if unfinished/unsatisfied then click back to wikitext and continue at 1
  4. save

Result: Virtually 100% error rate, except utterly random instances where your last comment was abnormally-saved without previewing.

The WMF's bias towards visual-editor is conflicting with real-world-use by the large majority of editors. Flow triggers continual hostility in users because almost every time we use it we have to stop and repair a mangled post because we started typing wikitext into VE. This is a never ending reminder to hate Flow more, each and every time we're forced to use it.

Event Timeline

Alsee raised the priority of this task from to Needs Triage.
Alsee updated the task description. (Show Details)
Alsee added a project: StructuredDiscussions.
Alsee subscribed.
Restricted Application added subscribers: StudiesWorld, Aklapper. · View Herald Transcript
Alsee set Security to None.

If you follow those steps (editing in wikitext, only clicking 'preview', clicking back to wikitext if dissatisfied, never making a change in VE), then do:

  1. Start a new Flow post.

it will be be in wikitext mode.

Please explain in what scenario(s) you see a 100% error rate.

Ok.... it only goes to the wrong mode when you preview AND make some final cleanup in VE mode. If it's a plain text typo I don't click back to wikitext to fix it. It's still a frustratingly high error rate. Flow shouldn't be starting in random modes every time I load it.

This is how we designed the feature, but I will put this in Team Discussion for us to consider whether we want to revisit.