Page MenuHomePhabricator

VisualEditor should warn when user enters wikitext but the editor is expecting plaintext
Open, LowPublic

Description

AIUI VisualEditor has a "wikitext markup detected" warning when the user types wikitext in the wrong place, but it seems to miss some common use cases (well, common at least in hu.wp where the Help: pages are still blissfully unaware of VE and people sometimes get confused and don't realize the tips refer to a different editor):

Event Timeline

Tgr created this task.Jul 30 2015, 5:01 PM
Tgr raised the priority of this task from to Needs Triage.
Tgr updated the task description. (Show Details)
Tgr added a project: VisualEditor.
Tgr added a subscriber: Tgr.
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptJul 30 2015, 5:01 PM
Jdforrester-WMF added a subscriber: Jdforrester-WMF.

The warning never was detected on paste (and can't reasonably do so). What would your suggested interface be?

DLynch added a subscriber: DLynch.Nov 10 2015, 10:58 PM

"Noticing if wikitext was contained somewhere in a massive paste and explaining our objection to it" is a bit awkward. But we could perhaps detect if the entire contents of the paste would match a sequence -- e.g. if someone literally just pasted in <ref> -- and just trigger the sequence.

Restricted Application added a subscriber: StudiesWorld. · View Herald TranscriptNov 10 2015, 10:58 PM
Elitre added a subscriber: Elitre.Feb 23 2016, 2:35 PM

"Noticing if wikitext was contained somewhere in a massive paste and explaining our objection to it" is a bit awkward. But we could perhaps detect if the entire contents of the paste would match a sequence -- e.g. if someone literally just pasted in <ref> -- and just trigger the sequence.

That's how it should work, I think? It wouldn't trigger a warning for anything which doesn't trigger it while typing, but yes, what David says is among the most common cases we see.
(Of course, the warning doesn't solve the problem entirely - we have seen people ignoring it. If a wiki had Citoid in place, VE would show the "blue dot" under the Cite menu, and people would discover that easier option for their referencing needs.)

Elitre added a comment.EditedFeb 23 2016, 3:49 PM

This may be another example of pasted code (didn't produce a working table, and isn't even nowikied).

Jdforrester-WMF changed the task status from Open to Stalled.Mar 7 2016, 8:09 PM
Jdforrester-WMF triaged this task as Low priority.
Jdforrester-WMF set Security to None.
Aklapper changed the task status from Stalled to Open.May 29 2020, 2:15 PM

The previous comments don't explain what/who exactly this task is stalled on ("If a report is waiting for further input (e.g. from its reporter or a third party) and can currently not be acted on"). Hence resetting task status.

(Smallprint, as general orientation for task management: If you wanted to express that nobody is currently working on this task, then the assignee should be removed and/or priority could be lowered instead. If work on this task is blocked by another task, then that other task should be added via Edit Related Tasks...Edit Subtasks. If this task is stalled on an upstream project, then the Upstream tag should be added. If this task requires info from the task reporter, then there should be instructions which info is needed. If this task needs retesting, then the TestMe tag should be added. If this task is either out of scope and nobody should ever work on this, or nobody else managed to reproduce the problem described in this task, then this task should have the "Declined" status.)

Aklapper removed Tgr as the assignee of this task.Jun 19 2020, 4:29 PM

This task has been assigned to the same task owner for more than two years. Resetting task assignee due to inactivity, to decrease task cookie-licking and to get a slightly more realistic overview of plans. Please feel free to assign this task to yourself again if you still realistically work or plan to work on this task - it would be welcome!

For tips how to manage individual work in Phabricator (noisy notifications, lists of task, etc.), see https://phabricator.wikimedia.org/T228575#6237124 for available options.
(For the records, two emails were sent to assignee addresses before resetting assignees. See T228575 for more info and for potential feedback. Thanks!)