VisualEditor/Feedback

From MediaWiki.org
Jump to: navigation, search
Share your feedback
Report bugs

Your feedback about VisualEditor

Start a new discussion about VisualEditor.
If you are reporting a problem, please include your web browser, computer operating system, and wiki skin (usually Vector, sometimes Monobook).

Use this page to tell the Wikimedia developers your ideas and issues about using VisualEditor. The Editing team welcomes your feedback and ideas, especially on user interface decisions and the priorities for adding new features. All comments are read, but personal replies are not guaranteed. This page uses LiquidThreads, so you need to click "Start a new discussion" (not the ordinary "Edit" link) to post your message.

Start a new discussion
First page
First page
Previous page
Previous page
Last page
Last page

Changelog abandoned?

Has the changelog/Status reports page been abandoned? https://www.mediawiki.org/wiki/VisualEditor/changelog seems completely inactive since late May, yet VisualEditor still keeps adding changes to weekly updates.

Since the change summaries are cryptic on that log, will we be seeing a return of the simplified change summary?

74.15.153.9614:18, 7 July 2015

NEW FEATURE: using Wikipedia for research

I suggest a link in the upper right hand corner that links to a page explaining how to get reliable information from WIKIPEDIA. On Wikipedia, moderators and editors try to maintain pages with footnotes citing sources to information (it's not always there, but we do our best). Students using Wikipedia do not really understand the value of the Wikipedia resource and how to use it. Wikipedia is like a clearing house for a wide range of ideas and concepts on a subject. Students can come to Wikipedia to get a broad conceptual range of what thoughts are on the subject, but they can not site Wikipedia, because it is not a first source. They need to follow the citations to find the first source on each idea they want to include in their research. We need to have a page that teaches people how to use Wikipedia for research.

In my mind, the best way to use Wikipedia for research is to come to Wikipedia to gather all the thinking on the subject. As you gather the pertinent points for your research, you need to note the sources associated with the items you read. For items you think might be true but that have no citation, you need to seek out sources. From that point, you have to go to the original sources for the actual data and research. Students do not understand how to use Wikipedia properly and it would be very helpful if we trained them. I suggest a link in the upper right hand corner titled HOW TO USE WIKIPEDIA FOR RESEARCH. This link would go to a page that trained them on best practices.
While we would all strive for Wikipedia to be so reliable that it could be cited, Wikipedia is really and open source knowledge base. In a way, being an open source knowledge base makes it more amazing than other knowledge bases. No one controlles what can be included and we all participate. By training students on best practices for research we help them learn how to use Wikipedia and we preserve it as an open source knowledge base and strengthen its significance.

autocitation

User agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/41.0.2272.101 Safari/537.36

can you add and auto citation feature to visual editor so all i have to do is paste URL and it looks up citation for references to put in articles

Jonnymoon96 (talk)01:24, 20 April 2015

Hello! This feature was completed last month and rolled out to a few wikis; which wiki were you thinking of?

Jdforrester (WMF) (talk)01:28, 20 April 2015

Some of User:Johnnymoon96's edits are at w:simple:, which does not have the citoid service set up.

Whatamidoing (WMF) (talk)02:32, 3 July 2015
 
 

Are there any plans to combine an inline differ with VE?

Are there any plans to combine VE with an inline visual differ like Extension:WikEdDiff?

VE is awesome, WikEdDiff is awesome. The mix of both would be super-awesome ;-)

Planetenxin (talk)11:02, 18 June 2015

It's been thought about, but I'm not aware of any plans to do this (at least, not in the near future). I think it's on the "probably someday" list.

Whatamidoing (WMF) (talk)02:24, 3 July 2015
 

pertanyaan

bagaimana cara memberi warna pada table?

Hanna Trisnawati (talk)14:37, 1 July 2015

Hello. If your question is about being able to change color for cells in a table with VisualEditor, please see [1]. Best,

Elitre (WMF) (talk)14:41, 1 July 2015
 

Visual Editor Save Page dialog Box

Hi there, When I click save changes in visual editor mode, the save page dialog box pops up with the summary textbox. When i click on the summary entry box or type anything, it selects my wikipage instead or type in my wikipage. Is there some function i have to turn on? or should i reinstall the visual editor?

Thanks! AT

AmazingTrans (talk)16:18, 24 June 2015

Several of us seem to be having this issue, see the issue titled "Cannot enter change summary, field loses focus."

What OS/Browser are you using? Most of us with this issue seem to be running Windows/Google Chrome. I'd like to try replicating this issue again, but I've already downgraded my wiki back to 1.24.

173.58.117.5918:26, 24 June 2015

I'm using Windows 7, Chrome 43.0.2357.130 m. MediaWiki 1.25.1 Looks like IE 11 seems to be working.

AmazingTrans (talk)19:48, 24 June 2015

To my correction, Actually IE11 stops working after i refresh. That's weird. I guess it depends on luck?

AmazingTrans (talk)21:53, 24 June 2015

Have you tried putting ""document.querySelector('input').focus()" into the console of the browser you're using? That seems like a very temporary fix for the problem, but it's still a giant hassle to have to do it every time to get it to focus.

173.58.117.5916:56, 25 June 2015
 
 
 
 

Installation issue with parsoid

RHEL 6

[root@APP02 node-v0.10.4]# git clone https://gerrit.wikimedia.org/r/p/mediawiki/services/parsoid Cloning into 'parsoid'... fatal: unable to access 'https://gerrit.wikimedia.org/r/p/mediawiki/services/parsoid/': Couldn't resolve host 'gerrit.wikimedia.org'


how to fix the above issue?

125.19.34.8607:17, 19 June 2015

You seem to be having network trouble. In particular, DNS does not seem to work as expected. https://gerrit.wikimedia.org/ is reachable from here, so I think it's specific to your network connection.

Gabriel Wicke (GWicke) (talk)18:48, 20 June 2015
 

Copying Table from Word

MediaWiki 1.25.1 VisualEditor REL1_25 Parsoid 0.2.0

When I copy a table from Microsoft Word and paste it in Visual Editor, it displays correctly as a table. But when I save the page the table turns into text only. If I edit again with VisualEditor the table appears formatted correctly. So, the table only displays correctly in VisualEditor, and not on the page.

198.179.137.21120:28, 15 June 2015

I believe this is phab:T85577 ("Pasted tables in VE-MW do not automatically get class="wikitable"") - I.e. it should look like a normal wiki table if (in wikitext) you change the first line to read:

{| class="wikitable"

Please let me know if it's more complex than that, and then I can file or find a more appropriate task. Thanks.

Quiddity (WMF) (talk)00:31, 18 June 2015
 

Cannot enter change summary, field loses focus

Issue

In the save page dialog, when I try to click the Summary input field, the field immediately loses focus. Instead, focus is put on the article text in the background (I can type there while the dialog is open).

Steps to reproduce:

  • Open any page and make a change through the VisualEditor.
  • Hit save button -> popup opens
  • Click the summary input text field

Specs

  • Chrome: 43.0.2357.81 m
  • Platform: Windows 8.1 Pro
  • MediaWiki: 1.25.1
  • Skin: Vector
89.146.39.3707:37, 4 June 2015

Currently experiencing the same issue, has anyone found a fix for this?

173.58.117.5923:10, 15 June 2015
 

Found a temporary fix for the time being: when the save dialog comes up, open up the developer tools in your browser and go to the Console (F12 -> Console in Google Chrome) and enter "document.querySelector('input').focus()"

Once you click on the text box again, it'll be in focus. Wonder if we can get a permanent fix/solution anytime soon, because this is a pretty big inconvenience right now.

71.93.147.13903:25, 16 June 2015
 

Note: Possibly Windows only? I cannot reproduce this, on Ubuntu, using Chromium 37 or Firefox 38, at my sandbox on this wiki.

Note2: Whilst the summary box is open, the only way I can get my cursor to focus on the document behind, is to use the [Tab] key.

Quiddity (WMF) (talk)22:16, 17 June 2015
 

Amazing, but wait...

This is a HUGE improvement over last editor. My only problem is with editing within the profile box section; for some reason you no longer have access too usual advanced editing tool (font size, adding references, inserting breaks etc. - it now has to be done manually (or of course through 'edit source')).

Heuh0 (talk)20:58, 31 May 2015

Hi Heuh0, If I understand correctly, you're describing how editing the templates in the top-right corner of many articles (aka Infobox), gives us the template-editor window (e.g. https://i.imgur.com/xmHMQu4.png ) which itself then requires wikitext/source inside it.

If that's right, then the issue is tracked at phab:T52182 ("VisualEditor: Add support for making some templates directly "visually editable" in the DOM, as if they were tables (e.g. infoboxes)"), and is on the planned feature list (but seems to be proving itself a harder challenge than first thought). Thanks for the feedback. :)

Quiddity (WMF) (talk)03:55, 4 June 2015
 

Actually, that's phab:T52355 ("Add support for editing templates' parameters as DOM elements, including supporting nested templates") which is very hard (but not quite as hard as T52182).

Jdforrester (WMF) (talk)21:25, 4 June 2015
 

No Notification If User Is Logged Out While Editing

In a wiki where a user is required to be logged in to save a page. If a page is being edited in the Visual Editor then in another tab the user is logged out of the wiki when the save button is clicked then the page responds by doing nothing but continuing to show the save button. It would be helpful if some notification was given to tell the user they need to log back in so that they can save the page.

98.17.210.412:42, 2 June 2015

This issue is tracked at phab:T50656 ("VisualEditor: Check for and warn user on unexpected badtoken event says they're now logged out"). Thanks for the report.

Quiddity (WMF) (talk)03:22, 4 June 2015
 

YES!! A huge improvement over the traditional editor

Thank You! Thank You! Thank You!

We've been using WYSIWYG editing in tons of programs for years. It slayed me the first time that I went to edit/write something in Wikipedia when I encountered the regular editor. While I've gotten used to it over time, the beta option is a giant leap forward. Nearly does away for the need of the preview button, though I like the idea that you kept the Edit Source option.

Hope this gets implemented soon!

Robertjm (talk)15:36, 23 May 2015

Thank you, Robertjm for this comment.

I assume you are active on English Wikipedia, where VisualEditor is available as a beta feature.

Trizek (WMF) (talk)14:48, 27 May 2015
 

You shouldn't be able to select some templates on Visual Editor

I don't know if this is a feature already, but i don't find it right know, so i go the lazy way and ask.

Some pages in the template namescape are not supposed to be transcluded directly on articles (e.g., they are parts of another templates, documentation subpages). There should be some kind of magic word that when is present on a page, the template selector on Visual Editor don't show them.

I hope i made myself clear with my caveman english

Ninovolador (talk)23:35, 30 April 2015

As far as I know, there is no such thing. Requested as I can see the benefit.

TheDJ (Not WMF) (talkcontribs)11:36, 1 May 2015
 

User:Ninovolador, thank you for this great idea. Please, can you give me links to some examples (some templates that are not supposed to be transcluded directly)? Good examples help the team solve problems.

Whatamidoing (WMF) (talk)02:51, 22 May 2015

Of course.

Besides obviously all the "/doc" subpages, look at an example of me trying to add a template to a random page. In this example i want to add a "Ficha de taxón" (taxobox)

here As you can see, all the dotted "templates" won't ever be transcluded directly.

Another issue it may arise is that you need to know the exact name of the template to find it, you should be able to search parts of the name (e.g., only search taxón and find it) but that is for another day.

Ninovolador (talk)16:44, 22 May 2015
 

Of course.

Besides obviously all the "/doc" subpages, look at an example of me trying to add a template to a random page. In this example i want to add a "Ficha de taxón" (taxobox)

here As you can see, all the dotted "templates" won't ever be transcluded directly.

Another issue it may arise is that you need to know the exact name of the template to find it, you should be able to search parts of the name (e.g., only search taxón and find it) but that is for another day.

Ninovolador (talk)16:45, 22 May 2015
 
 

If VE opens slowly

Recently was news that VE now rapidly opens. But for me it was not working. Every time I open a new wiki page and opened VE, for VE loads big js-file. I have long been using the visual editor in the firefox. Disable add-ons did not help, menu-options-privacy-delete cookies and delete cookies for ru.wikipedia.org not help. For me, it helped privacy-delete cookies and delete all cookies. Maybe it will help somebody else.

@Elitre (WMF): Thread:VisualEditor/Feedback/Feedback/reply I do not know because of what it was, but now, after removing all cookies VE opens quickly :)

Сунприат (talk)12:47, 9 May 2015

Thanks for this update. I was having some problems last week in Firefox; do any of the problems described here seem familiar to you?

Whatamidoing (WMF) (talk)02:42, 22 May 2015

No. Now I use only css and gadgets (which turns on and off when I need to), and all js-scripts put in my second account. So everything works a little faster.

Сунприат (talk)07:42, 22 May 2015
 
 

Some minor issues

Edited by another user.
Last edit: 09:02, 4 May 2015

Ich probiers mal auf Deutsch: Der VE hat sich seit Mitte letzten Jahres deutlich verbessert, danke erstmal dafür. Vor allem die Bearbeitung von Vorlagen und Bildeinbindungen finde ich komfortabel. Leider sind die Ladezeiten manchmal noch ziemlich lang und gerade bei längeren Artikel ist es störend, wenn für eine kleine Bearbeitung in einem einzelnen Abschnitt der ganze Artikel geladen werden muss, was dann ziemlich lang dauert.

Konkret aufgefallen sind mir noch folgende Dinge: Ich habe Probleme nach einem Wikilink "unverlinkt" weiterzuschreiben. Der Text danach wird erstmal dem Link zugerechnet. Den Link dort enden zu lassen wo ich will bedarf einiger Umstände, wie erst weiterschreiben, das dann markieren, als neuen Link kennzeichen und den dann entfernen. Das Drücken von Enter oder Esc hat nicht den gewünschten Effekt, dass man aus dem Link "aussteigt" und normal weiterschreiben kann.

Dann hatte ich beim Einbauen der Vorlage Commonscat gesehen, dass diese im VE unter dem Anführungspunkt erscheint und wiederum darunter die folgenden Links, was so nicht sein soll. Nach dem Speichern war die Vorlage aber korrekt hinter dem Anführungspunkt. Ein Darstellungsproblem des VE im Bearbeitungsmodus?

Außerdem vermisse ich wieder die "deutschen" Anführungszeichen (unten am Anfang, oben am Ende). Das hatte ich schonmal bemängelt und dann waren sie bei den Sonderzeichen. Jetzt kann ich sie wieder nicht mehr finden.

Falls das hilft: Ich verwende Mozilla Firafox for Linux Mint, auf Linux Mint Cinnamon, mit Vector Skin.

English translation by Gnom:

I will try in German: The VE has improved significantly since the middle of last year, so first, thanks for that. I fspecially find editing templates and inserting images comfortable. Unfortunately, loading times are sometimes still quite long and especially with longer articles it disturbs having to load the entire article for a small edit in a single section, which then takes quite long.

I specifically noticed the following things: I still have trouble continuing to write "unlinked" after a Wikilink. The text is then initally added to the Link. Letting the link end where I want it to end requires some hassle, like continuing to write first, then mark that, highlight as new link and then delete that. Pressing enter or escape does not have the desired effect of being able to "leave" the link and then continue to write normally.

Then while inserting the Commonscat template, I noticed that it shows up under the bullet point and then again the following links below that, which shouldn't be like that. After saving, the template was correctly behind the bullet point. A rendering problem of VE in the editing mode?

Also I miss the "German" quotation marks (at the bottom at the start, at the top at the end). I already pointed that out once and then they were among the special characters. Now I can't find them any more.

If that helps: I am using Mozilla Firefox for Linux Mint, on Linux Mint Cinnamon, with the Vector skin.

Don-kun (talk)18:46, 28 April 2015

Hi User:Don-kun, someone will look into your feedback as soon as possible. Thanks for leaving it here!

Elitre (WMF) (talk)10:15, 1 May 2015

Hi Don-Kun.

The "unlinked" text bug, is tracked at phab:T91285 (also known as: "link continuation rendering").

For the Commonscat and bullet point problem, would it be possible to take a screenshot? I'm afraid I don't quite understand, and my testing hasn't helped me to understand. Thanks!

The "German" quotation marks are back in the special characters list (http://i.imgur.com/JAIrAJF.png )

Quiddity (WMF) (talk)19:16, 15 May 2015

Also, the special character tool has been improved since last year: If you select a word, then a single click adds both quotation marks (before and after). Last year, you had to add them separately.

Whatamidoing (WMF) (talk)02:59, 22 May 2015
 

I also can't reproduce the problem with Commonscat and bullet lists in Firefox. User:Don-kun, ist das immer noch ein Problem?

Whatamidoing (WMF) (talk)03:19, 22 May 2015
 
 
 

issue with <tag> extension

In a private wiki (1.24.2) i have a self programmed extension that adds a new tag to wiki language, example: <mytag> The extension does return its content wrapped in <div></div> and therefore is editable via visual editor. Everything is working perfectly as long as i use a "begin"-tag and a "end"-tag with some content in between, like:

<mytag option="value">sometext</mytag>

In many cases it is not needed at all to have some content between begin and end tag, so it is possible to write the tag in "short" notation, like:

<mytag option="value" />

However when the "short" notation is used, after editing the tag with visual editor and nothing has been added in content field (is still empty), the complete tag will be removed.

Is this a known limitation of visual editor or do i need to fix my extension to make it properly editable in visual editor ?

Thanks for any hint in right direction.

Pzirnik (talk)15:19, 19 May 2015

Well, I don't know, so I've filed a bug report just in case. At least in theory it ought to be possible, because the <references /> tag is supported. User:Neil P. Quinn-WMF might be able to track down the answer.

Whatamidoing (WMF) (talk)02:56, 22 May 2015
 

visual editor and wikionary

i would love visual editor to be on Wiktionary and simple Wiktionary

Jonnymoon96 (talk)02:06, 14 May 2015

See meta:Requesting wiki configuration changes.

Helder16:30, 21 May 2015

Wiktionary is especially heavy in its use of templates, which is not VisualEditor's single most developed workflow.

There was a request last year from the English Wiktionary to allow only admins to opt-in via Beta Features, but this isn't possible. At this point, the team is likely to require evidence of community consensus. You might check in with the Swedish Wiktionary to see what they would recommend. It's been (opt-in only) there since late 2013.

Whatamidoing (WMF) (talk)02:39, 22 May 2015
 
 

Current problems

Edited by author.
Last edit: 08:12, 21 April 2015

The one problem sometimes (not always) appears using editor: If you prefer to keep bibliographical data out of the endnotes, you have to use ref tags like "#xxx" to link to a bibliography. Often the editor refers to the whole page, so that it will be loaded again. For now I have to switch to the source editor in order to fix it. It would be more elegant, if the window of a note (<ref>) finds the anchors automatically. If they are chosen, there should be no link to the identical page (which causes reloading). By the way, if you use bibliography lists, it is not very useful that cite templates are always in a note. Within the beta editor, this forces to switch to the source editor.

Platonykiss (talk)06:56, 21 April 2015

Right now the editor needs some time to open and it jumps to the right position not before you try to change something and it needs some time to place the cursor (never on the first attempt). Sometimes it does not open at all, and if opened, the open window is sometimes unstable.

Platonykiss (talk)06:59, 21 April 2015

This is an old bug: Whenever beta editor has saved changes, a second reload is necessary to let notes pop up again.

Platonykiss (talk)10:13, 21 April 2015

Another bug report:

I would like to add, that I get several times an error report, while opening the beta editor a second time. It tells me that I am not working an the current version on the page (which is not true!). I also checked the history and there was no interference with another user.

Platonykiss (talk)08:41, 22 April 2015

Hey Platonykiss, not sure if this is a problem with VE, but I'd encourage you to add details (example page, browser, operating system, skin...) so that User:Jdforrester (WMF) can tell us what's going on. Regards,

Elitre (WMF) (talk)17:24, 24 April 2015

Quite frankly, I do not know, what is going on...

You do the changes, and right now Betaeditor works so badly (nearly like MS Word, doing a lot of things that it should not do), that I do not longer use it. It would be a waste of time!

Concerning the language tool, the offer for Greek characters is not sufficient. It should be polytonic Greek. If you prefere to spare buttons, the diacritics should be used in combination (unlike you do now).

Platonykiss (talk)16:22, 8 May 2015
 
 
 
 
 

Citing by identifier

Hi! I like how the citing template in the non-visual editor lets you search the source by isbn or doi and fills in the rest of the info. That's the main reason i use "edit source" more. Is there anyway to make this feature available in the visual editor? --Frederika Eilers (talk) 15:02, 2 May 2015 (UTC)

Frederika Eilers (talk)15:02, 2 May 2015

Hi Frederika. Several DOIs should be already working in Citoid (if you find any which don't, please report them here!). Support for ISBN is definitely planned. Thank you,

Elitre (WMF) (talk)06:33, 4 May 2015
 

Visual Editor Fails To Load Unknown dependency: mediawiki.language.specialCharacters

It has been really difficult to get this far but it seems the visual editor is finally loading up correctly...well kinda. The loading bar gets about 75% of the way across then it freezes. There are no php errors just a single error in the browsers console

Uncaught Error: Unknown dependency: mediawiki.language.specialCharacters

load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20150502T1…:156

Im currently running 1.24.2. It seems like an obvious solution, but i dont know where to get and add to the dependency to

95.45.40.1613:24, 2 May 2015

Seems to me like you have a version of VisualEditor that is newer than the your MediaWiki Core, since mediawiki.language.specialCharacters was introduced in 1.25. You need to use the same version of core and extensions.

TheDJ (Not WMF) (talkcontribs)10:31, 3 May 2015
 
First page
First page
Previous page
Previous page
Last page
Last page