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)

#dpl template allows more than one categories, but VisualEditor keeps only the first one

Gkovacsp (talkcontribs)


I add a dpl template with the text based wiki editor using a few parameters, like:



Things work as expected.

If I edit this page with VisualEditor, then it will keep only the first category value and remove the rest.


TheDJ (talkcontribs)

I don't think DPL is supported by visualeeditor and/or parsoid.

Gkovacsp (talkcontribs)

Is there an alternative to dpl which is supported by VisualEditor?

Jdforrester (WMF) (talkcontribs)

No. The maintainers of the DPL extension and its alternatives haven't done anything on this, AFAICT, sorry.

Reply to "#dpl template allows more than one categories, but VisualEditor keeps only the first one"

Suggestion: Make the Use VisualEditor diff feedback tool add the diff to page

2 (talkcontribs)


It seems that currently the Diff tool just links people to the diff page, and many users may not know anything about diffs.

Proposed solution:

Use feedback tool add the diff to page


Use Help:Structured Discussions/Preloading .

A Feedback form with placeholder fields or simply text (e.g. "Problem: , Where: Using what feature", would also be a good idea. The current one is just adds a link, and is probably the source of a lot of empty feedback for people who just experiment with clicking buttons. (talkcontribs)

Example of a confused user who clearly doesn't know how to find a diff:

Funny thing is that itself doesn't even have reasonable documentation about how to link to a diff. Despite a lot of help pages / feedback and even the how to report bug page asking for "diffs".

It seems like a classic case caused by the Burden of experience.

Reply to "Suggestion: Make the Use VisualEditor diff feedback tool add the diff to page"
Epìdosis (talkcontribs)

An edit like this is suspect in my opinion: I think the IP didn't want to remove all these links, so maybe the Visual Editor did it by itself. I remember another similar case some months ago, I can maybe find the link if it may be useful.

Reply to "Removal of links"
Jmarmi (talkcontribs)
Agent d'usuari: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.106 Safari/537.36


Estic intentant pujar imtages per il·lustrar el meu article i em trobo que algunes les puc publicar mentre que altres no em deixa l'aplicatiu. Em dóna el següent error: Cross-wiki upload filter. Com ho puc sol·lucionar?

Reply to "Publicació d'imatges"
Luislizardim (talkcontribs)

Where do I find the references ?

Reply to "Where do I find the references ?"

Words sometimes get messed up when something is pasted

Summary by Whatamidoing (WMF)
Epicgenius (talkcontribs)

Originally pasted here:

Description Pasting distorts the words in the sentence around it.
Intention: I was trying to paste a sentence
Steps to Reproduce: #First open up a page with visual editor
  1. Then copy something
  2. Finally paste it onto another page where the visual editor is already active.
Results: The words got jumbled into a bunch of gibberish. E.g. in this diff, "Prior to this ban, there were debates" was changed to "T Prior to teis ban, thre hweredebates"
Expectations: The reference to be pasted properly.
Page where the issue occurs Some pages whenever Visual Editor is open, but occurs randomly.
Web browser Google Chrome Version 67.0.3396.87 (Official Build) (64-bit)
Operating system Windows 10
Skin Vector

I don't know why this occurred. A fix or workaround would be appreciated. Thanks.

Whatamidoing (WMF) (talkcontribs)

Is this still happening?

Does it happen if you're editing in safemode?

Epicgenius (talkcontribs)

@Whatamidoing (WMF) I haven't encountered this problem in a while, as it only happens sporadically.

Edit: To clarify, I haven't seen this problem since I last posted this. However, it does happen once in a while, especially when I make large changes, or copy and paste references.

Whatamidoing (WMF) (talkcontribs)

I've had this kind of symptom happen here (i.e., in Flow replies), but I can't figure out how to trigger it on purpose (and it might not require pasting anything). I'll file a "placeholder" task in Phabricator, just in case we come up with some more information. (talkcontribs)

I have also encountered this issue. Not only by copy pasting, but also by typing a text (which looks fine) and then saving (which has some letters in the incorrect spot). While typing, I would then notice the editor sometimes jerking to the top of the page and then back to the place being edited

Reply to "Words sometimes get messed up when something is pasted" (talkcontribs)

Here's a screenshot about what's happening everytime I try to create or edit a page. The blue bar appears, load until ~70% then freeze.

I tried to check what's happening with firefox & chrome dev tools. Everything seems fine, here's a sample of a request json response.

{"visualeditor":{"result":"success","notices":["<p>You have followed a link to a page that does not exist yet.\nTo create the page, start typing in the box below (see the <a class=\"external text\" href=\"\">help page</a> for more info).\nIf you are here by mistake, click your browser's <strong>back</strong> button.\n</p>"],"checkboxes":{"watch":"<input name=\"wpWatchthis\" type=\"checkbox\" value=\"1\" tabindex=\"1\" accesskey=\"w\" id=\"wpWatchthis\" />&#160;<label for='wpWatchthis' id='mw-editpage-watch' title=\"Add this page to your watchlist [w]\">Watch this page</label>"},"links":{"missing":["Cpage"],"extant":[]},"protectedClasses":"","basetimestamp":"20150813153540","starttimestamp":"20150813153541","oldid":0,"content":""}}

It's like he doesn't try to load the next page, the form for page edition / creation.

It's a private wiki. MediaWiki's 1.25.2. I got VisualEditor-REL1_25-c947b49.tar.gz and UniversalLanguageSelector-REL1_25-7661826.tar.gz. Here is my conf

### UniversalLanguageSelector (prérequis Parsoid)     # wfLoadExtension( 'UniversalLanguageSelector' );     require_once "$IP/extensions/UniversalLanguageSelector/UniversalLanguageSelector.php";     $wgULSGeoService = false;     $wgULSEnable = false;     $wgULSIMEEnabled = false;

    ### VisualEditor     wfLoadExtension( 'VisualEditor' );     # require_once "$IP/extensions/VisualEditor/VisualEditor.php";

    $wgVisualEditorSupportedSkins = array( 'Vector', 'Apex', 'Monobook', 'Minerva' );

    # Enable by default for everybody     $wgDefaultUserOptions['visualeditor-enable'] = 1;

    # Don't allow users to disable it     # $wgHiddenPrefs[] = 'visualeditor-enable';

    # OPTIONAL: Enable VisualEditor's experimental code features     #$wgDefaultUserOptions['visualeditor-enable-experimental'] = 1;

    # URL to the Parsoid instance     # MUST NOT end in a slash due to Parsoid bug     $wgVisualEditorParsoidURL = 'http://localhost:8000';     $wgVisualEditorParsoidHTTPProxy = false;

    # Interwiki prefix to pass to the Parsoid instance     # Parsoid will be called as $url/$prefix/$pagename     $wgVisualEditorParsoidPrefix = 'wikidiff';

    # # Namespaces for VE     #$wgVisualEditorNamespaces = array_merge($wgContentNamespaces, array( NS_USER ));     $wgVisualEditorNamespaces = $wgContentNamespaces;

    # Timeout for HTTP requests to Parsoid in seconds, and for serializationcachetimeout     $wgVisualEditorParsoidTimeout = 200;     $wgVisualEditorSerializationCacheTimeout = 3600;

    # Réglage parsoid pour wiki privé     #     $wgSessionsInObjectCache = true;     $wgVisualEditorParsoidForwardCookies = true;

Anyone can tell me what the hell is wrong ? It's been two long days...

Winand (talkcontribs)

Did you resolve that issue somehow? When I turn on $wgResourceLoaderDebug VisualEditor loads. But without debug mode it freezes at 70%.

Reply to "VisualEditor won't finish loading"

Automatic reference generation from doi gives incorrect date formatting

Hemiauchenia (talkcontribs)

When automatic citation by doi is used, the date given in the generated reference is given the format of year-month in numbers, so for instance March 2004 is given as 2004-03, which throws up a bad date Cs1 error.

Whatamidoing (WMF) (talkcontribs)

This is a known problem. The date isn't "incomplete", as there is no day of publication to include in the date; it's just a format that CS1 templates don't accept. If memory serves, the Citoid devs and the CS1 template programmers were talking about having the template interpret the number, so that if the template parameter said 2004-03, then the template would display as "March 2004". I don't know if this is being worked on, or if they decided to not do it (e.g., for fear of interpreting a typo as meaning "March 2004" when it ought to have been "3 January 2004").

Reply to "Automatic reference generation from doi gives incorrect date formatting"
Carl.denieul (talkcontribs)
Whatamidoing (WMF) (talkcontribs)
Trizek (WMF) (talkcontribs)

The article has been successfully published since that feedback.

<figure-inline> tags appearing after editing pages with images

8 (talkcontribs)

When I edit an article that contains images the image gets wrapped with <figure-inline> and </figure-inline> tags. Is there any way to turn that off? Because I always have to remove that stuff with the Wiki source code editor.

TheDJ (talkcontribs)

please link to where this is happening. (talkcontribs)

I'm afraid I cannot send you a link to our wikis since they are all only internally reachable. So all you can do is try it out yourself. (talkcontribs)

I've found out something interesting. This error occured after the Update of MediaWiki 1.30! Before that, Visual Editor worked flawlessly. Is there any way to correct this mistake? Otherwise I will have to downgrade our wikis to Version 1.29.2.

Whatamidoing (WMF) (talkcontribs) (talkcontribs)

My copy of Mediawiki is having this problem as well. I recently updated VisualEditor to the 1.31 version alongside the rest of the wiki components and now I'm having the problem: Link: (talkcontribs)

I was just informed that the fix is allegedly to update your Parsoid, if you update your VE and not your parsoid the tags get generated and aren't parsed correctly

Matma Rex (talkcontribs)

<figure-inline> tags for inline images were introduced in a relatively recent version of Parsoid (September 2017); previously they were wrapped in <span> tags.

This issue sounds like something that might happen if you updated your VE (so that your new version of VE generates <figure-inline> and expects Parsoid to handle them), but not your Parsoid (so your old version of Parsoid doesn't know how to handle them yet and outputs them as-is to wikitext).

The solution is probably to upgrade your Parsoid, or if you can't do that (especially if you installed from a Debian/Ubuntu package, I think they are not updated very often), you'll have to downgrade your MediaWiki/VisualEditor :(

(Relevant commits for context/dates:

Reply to "<figure-inline> tags appearing after editing pages with images"