VisualEditor/Feedback

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)

VE is adding incorrect wikitext <br /> for breaks versus simpler <br>

3
Timeshifter (talkcontribs)

I noticed this when I clicked the enter key in Visual Editor to separate some stuff I was working on in my sandbox. This is a bad idea.

People have come to help pages such as en:Help:Sorting on English Wikipedia and tried to replace all <br> tags with <br />. We had to revert all their work and explain to them that we are trying to make things simpler for editors, not more difficult.

By the way, why is this editing window making editing more difficult by not having a button for nowiki tags as in Wikipedia? Developers should be trying to make things easier. Now I have to go to an editing window on Wikipedia to find the correct nowiki wikitext, copy it, and then come back here. I often wonder where to put the slash. I don't have this stuff memorized.

And this crap editor keeps messing up the nowiki tags I try to enter.

Frlara (talkcontribs)

How can I add a line break from VE? I tried shift-enter and all other key combinations, but it always starts a new paragraph. I also didn't find it in the toolbar.

Timeshifter (talkcontribs)

I tried to retrace my steps, and the only thing remaining that produces this for me is when pasting in a table into the visual editor in a certain way. I did it earlier today, but I can't duplicate that way now! So I think this remaining problem can safely be ignored since it is now so obscure.

The other day I was working on editing a table, and I think at the same time I was editing en:Help:Table and writing tips in the Visual Editor section at the end. So I was paying close attention to any screw ups on my part or the part of the Visual Editor. I vaguely remember that the problem was happening more often then. So maybe it has been fixed since I started this thread 11 days ago.

Reply to "VE is adding incorrect wikitext <br /> for breaks versus simpler <br>"

Feature: Recovery of edits after a crash

1
Jamespharvey20 (talkcontribs)

I've been having system problems lately, and crashing a lot. Before using VisualEditor, Chromium and Firefox saved my edits when restoring sessions, as long as I am using a persistent login. When using VisualEditor, they are unable to do this. Some type of recovery of in-process edits would be a really nice feature. I think at least for the time being, the lack of this feature is going to prevent me from using it anymore, maybe forever.

Reply to "Feature: Recovery of edits after a crash"
Frlara (talkcontribs)

How can I add a line break from VE? I tried shift-enter and all other key combinations, but it always starts a new paragraph. I also didn't find it in the toolbar.

Reply to "Line breaks"
68.186.118.80 (talkcontribs)

Can text be colored ?. If not, is it in the plans ?

Reply to "Can text be colored ?"
Christophecourtois1964 (talkcontribs)
Reply to "Logo a changer"
15.211.201.90 (talkcontribs)

Receiving the following error when trying to edit pages:

Error loading data from server: internal_api_error_Exception: [4bb4c6c281aa39d960f6ef94] Exception caught: PHP cURL extension missing. Check https://www.mediawiki.org/wiki/Manual:CURL. Would you like to retry?

This is a new upgraded installation of MW from 1.28 to 1.31. I have Installed VisualEditor-REL1_31-6854ea0 along with Parsoid version 0.10.0 on MW 1.31.

LocalSettings.php:

# VisualEditor Settings

wfLoadExtension( 'VisualEditor' );

// Enable by default for everybody

$wgDefaultUserOptions['visualeditor-enable'] = 1;

// Optional: Set VisualEditor as the default for anonymous users

// otherwise they will have to switch to VE

// $wgDefaultUserOptions['visualeditor-editor'] = "visualeditor";

// Don't allow users to disable it

$wgHiddenPrefs[] = 'visualeditor-enable';

// OPTIONAL: Enable VisualEditor's experimental code features

#$wgDefaultUserOptions['visualeditor-enable-experimental'] = 1;

$wgVisualEditorParsoidURL = 'http://localhost:8142';

$wgVirtualRestConfig['modules']['parsoid'] = array(

    // URL to the Parsoid instance

    // Use port 8142 if you use the Debian package

    'url' => 'http://localhost:8142',

    // Parsoid "domain", see below (optional)

    'domain' => 'localhost',

    // Parsoid "prefix", see below (optional)

    'prefix' => 'localhost'

);

$wgEnableAPI=true;


Parsoid Configuration:

# Configure Parsoid to point to your MediaWiki instances.

        mwApis:

        - # This is the only required parameter,

          # the URL of you MediaWiki API endpoint.

          uri: 'http://localhost/mediawiki/api.php'

          # The "domain" is used for communication with Visual Editor

          # and RESTBase.  It defaults to the hostname portion of

          # the `uri` property below, but you can manually set it

          # to an arbitrary string.

          domain: 'localhost'  # optional

          # To specify a proxy (or proxy headers) specific to this prefix

          # (which overrides defaultAPIProxyURI). Alternatively, set `proxy`

          # to `null` to override and force no proxying when a default proxy

          # has been set.

          #proxy:

          #    uri: 'http://my.proxy:1234/'

          #    headers:  # optional

          #        'X-Forwarded-Proto': 'https'

Reply to "PHP cURL Extension Error"
O revolucionário aliado (talkcontribs)
FrancisAkio (talkcontribs)
Reply to "problems"

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

4
197.235.56.25 (talkcontribs)

Issue:

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

Alternative:

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.

197.235.56.25 (talkcontribs)

Example of a confused user who clearly doesn't know how to find a diff:https://www.mediawiki.org/w/index.php?title=Topic:Uiu1bcfx0jvbe3jg&action=history

Funny thing is that Mediawiki.org 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.

Whatamidoing (WMF) (talkcontribs)

From inside the editor (i.e., you're looking at the diff, but you haven't published your changes yet), it's impossible to create the diff URL. The revision id that's needed for the URL isn't assigned until the change is saved.

197.235.232.83 (talkcontribs)

This is true, but visualeditor (and all sensible editing tools) always knows what the previous / current revision was, from a user's perspective. Linking to that is better than simply linking to the page itself.

In fact, in many cases it will be more productive to link to that. Sometimes the user is having trouble saving the page, so the revision they are editing is a more useful reference than the current page simply because in many cases the page be edited several times.

Reply to "Suggestion: Make the VisualEditor diff feedback tool add the diff to page"

Is it possible to turn off the notices on visual editor?

4
Thedonquixotic (talkcontribs)

EVERY SINGLE TIME I open a new topic that hasn't been made before I get that little pop up telling me that I'm making a new page. I know ! It's like Navi from Zelda. Yeesh!

Can I turn it off?

TheDJ (talkcontribs)

These are likely editnotices, which are specifically added by the community of editors to show up every single time when editing a page or a namespace. Talk to your local community if there are notices that you think should not be shown.

Thedonquixotic (talkcontribs)

@TheDJ I'm learning development and decided to start my own personal self hosted mediawiki wiki so I am the guy in charge of that, but I don't know how to do that, and I'm having trouble finding documentation on how to turn them off. Any pointers?

197.235.232.83 (talkcontribs)
Reply to "Is it possible to turn off the notices on visual editor?"

Input of Korean letters to a single-clicked table cell

1
Doyoon1995 (talkcontribs)

When typing Korean letters into a single-clicked table cell, the first one is always ignored. When I type "cat" into a single-clicked cell, all three letters are actually typed into the cell. For "고양이", the result is "ㅗ양이" with the first component "ㄱ" missed. Could somebody help?

Reply to "Input of Korean letters to a single-clicked table cell"