Jump to navigation Jump to search

About this board

Post your feedback about using the visual editor.

If you have never provided feedback before, you can learn how to do it effectively. If you are reporting a problem directly on this page, please include your web browser, computer operating system, and wiki skin (usually Vector, sometimes Monobook). The feedback tool within the visual editor will include your user agent details instead.

You can use this page to tell the Wikimedia developers your ideas and issues about using the visual editor: this is the only feedback page actively monitored by WMF staff. The Contributors team welcomes your feedback and ideas, especially on user interface decisions and the priorities for adding new features. All comments are read, in any language, but personal replies are not guaranteed: the team will try and go through reports here at least once a week. Need more attention? Report directly in Phabricator. Please note that the Wikimedia Foundation does not provide support for installing VisualEditor on third-party wikis. Please report bugs involving Parsoid at Talk:Parsoid instead.

You may also want to read a guide to optimize the visual editor's experience on your site, which details work necessary on the community side (such as translating or setting up citation systems).

View open developer tasks Report a new bug in Phabricator Join the IRC channel Test the visual editor! (no account required)

Edit by the VisualEditor flooded an article with inappropriate <span lang="ta" dir="rtl">...</span> constructs

AFBorchert (talkcontribs)

I do not use the visual editor myself but just noted that this good-faith edit which was tagged as visual edit flooded an entire Wikipedia article with inappropriate <span dir="rtl" lang="ta">...</span> constructs.

TheDJ (talkcontribs)

User error (or user malice). He did "select all" and then chose Formatting -> Language -> Tamil from the menu.

Reply to "Edit by the VisualEditor flooded an article with inappropriate <span lang="ta" dir="rtl">...</span> constructs"
Bdijkstra (talkcontribs)

On many wikis, directly inserting the magic word __DISAMBIG__ (or equivalent) is undesirable, a template is to be used instead. Can the disambiguation page tick box (Visualeditor-dialog-meta-settings-disambiguation-label) be disabled or customized to insert something else?

Whatamidoing (WMF) (talkcontribs)

What's the practical purpose for preferring a local template to core MediaWiki magic words?

Bdijkstra (talkcontribs)

What's the practical purpose for inviting users to violate local policy? The wiki communities get to decide what a disambiguation page is supposed to look like. When direct insertion of the magic word is undesirable, the tick box is a pitfall.

Reply to "Disambiguation tickbox"


6 (talkcontribs)

First Part of the question answered. Hope this will help another newbie.


   " Call": "☎",

   " Msg  ": "◎",

   " Msg-Rtnd": "◉"


When saved, it changed the Visual_editor insert special character box and makes buttons to insert the pretty icon pictures.. Rather clever.

Now. I don't know how to make the inserts lager, and I don't know how to colorise them.

TheDJ (talkcontribs)

HTML spans with CSS can do to both of those, but they are not part of characters and as such cannot be provided by quick access. In general we do not tool formatting options like colors, since they are not considered suitable for usage outside of carefully crafted templates.

If you really want that, you can create your own buttons or menu for that, but it is a tad harder to make those.

Whatamidoing (WMF) (talkcontribs)

Where "we" means "the Wikipedias". Other wikis have more use for colors.

There are several feature requests for this, including phab:T54645 and phab:T66376. There's also a ticket somewhere in which we request background colors in tables, and if there is any justice in the world, it should include as an example a link to a diff of the product manager adding colors to a page by hand – the same product manager who told me that nobody really needed to be able to add colors to tables. ;-)

TheDJ (talkcontribs)

There is another reason not to be a fan. Accessibility is very hard to ensure if everyone can use colors. Using colors generally, is what people do when they have no way to communicate emphasis, but that's what <strong> and <em> are for. And those can be styled. (They too are not part of default wiki toolbar however)

Whatamidoing (WMF) (talkcontribs)

Accessibility is also compromised when we expect people to keep their place in a 20-column data table, with nothing to help their eyes stay on the same line as they scan across. Green bar paper was invented for accessibility reasons, and the same needs exist on screen.

Jdforrester (WMF) (talkcontribs)

I agree that 20-column tables are incompatible with the goal of accessibility, and should be broken up.

Reply to "MediaWiki:Visualeditor-quick-access-characters.json"

Misuse of author name fields in cite web coding

Mandruss (talkcontribs)

According to this citation created by a different user, the source has two authors named CBC News Mar 18 and 2019 9:56 PM ET | Last Updated: March 19. I submit that this is implausible. I contacted the user about the problem and they shift the responsibility for citation quality to VE.

TheDJ (talkcontribs)

Citation resolution by Reftoolbar and and Visual Editor are handled by citoid, which in turn uses Zotero translators (and I can confirm by using the desktop app, that Zotero imports the same information). There is information about dealing with problems in Zotero translators, available here and here.

Whatamidoing (WMF) (talkcontribs)
Mvolz (WMF) (talkcontribs)

Unfortunately yes; this is a zotero bug and I've reported it but not much movement. At present the author field in the source website has that info in it, so I'm not sure much can be done about it besides creating a custom translator for the website.

Reply to "Misuse of author name fields in cite web coding"

Erreur à l'utilisation "no vrs"

Titanscity (talkcontribs)


J'utilise Firefox 52 sur Windows 10 et mon mediawiki est en monobook (

J'ai installé visual editor et modifier le fichier localsettings.php mais lors de la modification d'une page, la barre de chargement bleue apparait, commence à se remplir puis j'ai un message d'erreur :

Erreur lors du chargement des données du serveur : no_vrs: The VirtualRESTService for the document server is not defined; see Voulez-vous réessayer ?

Mon médiawiki est installé sur une serveur mutualisé. J'ai cru comprendre qu'il fallait d'autres installations ? J'avoue que l'installation de cette extension est un vrai casse-tête et l'expérience utilisateur est détestable :D ce n'est pas à la portée de tout le monde d'en faire l'installation a priori !

Est-ce que quelqu'un *lance une bouteille à la mer* saurait m'aider pour configurer/utiliser l'éditeur visuel ?

Merci d'avance !


Whatamidoing (WMF) (talkcontribs)

I'm sorry; I don't know how to install this. Perhaps you would like to post at Project:Support desk?

Zer00CooL (talkcontribs)

Tu as de nouvelles informations depuis ? Je cherche également.

DThomas76 (talkcontribs)

Pareil de mon coté, et rien à voir avec un wiki privé ou non je pense car le mien je l'ai réinstallé pour qu'il soit plus privé

Reply to "Erreur à l'utilisation "no vrs""

Como gravar o documento ainda em ediçao

Chevra M (talkcontribs)
Whatamidoing (WMF) (talkcontribs)

@He7d3r, can you look at this? Perhaps it was an AbuseFilter or spam blacklist problem.

Jiangchaowiki (talkcontribs)

perhaps was an abuse

Reply to "Como gravar o documento ainda em ediçao"


1 (talkcontribs)

Are there examples of how to enter information into this page. Is is rather non intuitive...


Alzi24 (talkcontribs)

When browsing through the various documentation pages, it seems as if development has been suspended two years ago. Sorry for the maybe silly question, but what is the current status of the VE? Are there plans for relaunching and further development? Or am I completely wrong and the VE is alive and healthy, just the documentation a little bit outdated?

AKlapper (WMF) (talkcontribs)

What exactly makes you think that development has been suspended? :) Documentation updates are welcome if you find something outdated!

Alzi24 (talkcontribs)

It's just what I am worrying about when viewing ...

and so on. It is all a little bit difficult to understand for s.o. outside the WMF and/or developer team.

I might be completely wrong - alright then, the better. We are just a small private wiki and have installed the VE (which is "still experimental" for outside Wikimedia, as I read) to launch for a usability test. I would not appreciate investing time in testing and asking for support, if I'll hear it will be ceased afterwards. On the other hand, outdated pages might be a manpower bottleneck just the same as with our contributors ...

Finally, the Talk pages consultation 2019 and look to me as if there were bigger problems the WMF has to deal with, than some minor VE bugs and requests.

Jdforrester (WMF) (talkcontribs)

VE (which is "still experimental" for outside Wikimedia, as I read)

Correct. The Foundation's budget priorities don't align with us making the epic re-engineering of VE into a state that it's as easy to install as the rest of the MediaWiki, and so it would be irresponsible for us to recommend it to low-end third party users.

Note that there's no-one who is paid by the Foundation to provide support to anyone for any part of MediaWiki, core or extensions, let alone VE. The support that do people get is generally either staff working in their personal time, or other members of our wonderful developer community, both volunteers and those paid by other organisations.

To help the team out, I have updated the three old status systems to explain to people that the are obsolete , noted that there aren't any VE-specific engineering update systems any more , and removed the reference to when the 2017 editor's integration last changed . Thanks for spotting the issues, and sorry it caused you concern!

Reply to "Current project status?"

Visual editor table behavior

Summary by Whatamidoing (WMF)
Redfiona99 (talkcontribs)


So I was working on the table in

Because the boxing record table is quite complicated, I thought I'd used Visual Editor to do it. It works quite well, except for the second column titled "results". The second column contains a template, and if you just copy from the row above you end up with a shifted table like the second table here - I'd want it to look like the third table.

It's an easy enough manual fix, you just have to move the |{{ yes 2 }} Win down a line and then it realigns itself properly, but I'm not clear on why copying and pasting would cause it not to do that, when it's not a problem if you copy and paste any of the other boxes.



Whatamidoing (WMF) (talkcontribs)

I'm glad to hear that it's an easy fix, because I don't realistically expect this bug to be fixed for a long time. I think we filed a similar request in 2014 over the {{yes}} templates. As for why this class of templates is complicated, they insert some table formatting code, but they don't make a full table, so the template is partially removing control over the table from the visual editor, but it's still expected to manage the table. So I think it can't always figure out what's going on. Under the circumstances, the only real surprise is that it isn't screwing up more of it.

Redfiona99 (talkcontribs)

Thanks for the really clear explanation. Even with the fix it's a lot quicker than writing it all out by wikitext and I now know when to expect similar behaviour.

Reply to "Visual editor table behavior"

Ошибки в редакторе. Bugs.

Concrete Stocking (talkcontribs)
Браузер: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.110 Safari/537.36


1. Если поставить ударение любым из имеющихся шаблонов в текстовом редакторе, а затем переключиться в визуальный, то шаблон будет показан как текст, ударение не отобразится.

2. Если из текстового редактора перейти в визуальный, после чего нажать "Записать страницу", то кнопки для быстрого описания изменений (викиф, оформл, стил и остальные) не отобразятся.

  1. If you put a stress with a template in the common editor and then switch to the visual one, the stress won't appear, you'll just see the template as a text instead.
  2. If you switch from the common editor to the visual one, the buttons for a short description of your changes won't appear. (I don't know if there are any in the English Wikipedia, but there are some in the Russian one)
TheDJ (talkcontribs)
Concrete Stocking (talkcontribs)
  1. sure! stress (in this case) = ''the emphasis you put on one part of a word. In the word 'blanket', the stress is on the first syllable.''
  2. got it
Whatamidoing (WMF) (talkcontribs)

Can you give me a link to a template for adding emphasis to text?

Concrete Stocking (talkcontribs)

I use the Russian wiki, so the page is in Russian. (if you save the changes or click 'show preview', the emphasis can be seen, but when you switch from one editor to the other, it can't)

Whatamidoing (WMF) (talkcontribs)

The only thing in that template is:


That's U+0301, the "Combining Acute Accent". That character doesn't result in italics, bold, or <em>. Is it meant to be this?


That's U+0027, the straight "Apostrophe".

Reply to "Ошибки в редакторе. Bugs."