VisualEditor/Feedback/LQT Archive 1

__NEWSECTIONLINK__

 Your feedback about the visual editor developer prototype

This page is a place for you to tell the Wikimedia developers what issues you encounter when using the visual editor sandbox. Please note that this is still an early prototype which cannot yet edit or save existing pages and has many known issues. We do welcome your feedback and ideas, especially on some of the early user interface decisions we're making!

[//www.mediawiki.org/w/index.php?title=Visual_editor/Feedback&action=edit&section=new Add a new comment] – View known bugs – Report a new bug in Bugzilla

Latest status update



Archives (older archive dates indicate date of initial comments and may span several months; newer archives span one month per archive and are generated by MiszaBot):

Feedback by users that see no feedback link
Some feedback by German users here: de:Wikipedia Diskussion:Kurier

Usability
It's great that you're working on a visual editor.

I've trained non-technical people on wikis and I know there is a strong reluctance for people to do any editing once they see the wiki-markup.

In this spirit, I might suggest putting the 'advanced editor' tools like Wikitext View, JSON View, etc under a single drop-down. My sense is people will see those options, not understand what they mean and decide not to touch anything for fear they'll break it.

I look forward to showing people how easy it is to use the simplified editor.

Wikitext view
User agent: Mozilla/5.0 (X11; Linux i686; rv:9.0.1) Gecko/20100101 Firefox/9.0.1 Iceweasel/9.0.1

This news editor is great. For backward usability (keeping the ability to edit as wikitext) that would be greater if the "Toogle wikitext view" would allow directly editing wiki syntax (and see the result in the visual editor) 193.49.225.25 16:15, 4 January 2012 (UTC)


 * First, absolutely agree that this is an awesome advance. Second, now I can't help being hungry for more, and the idea by the above contributor is right on.  Not every feature will be available in the new visual editor, and we will still need wiki markup for a while; working in markup and seeing directly the change made makes it much easier to learn markup features.  The small amount of wiki markup I've taught myself is through painful back-and-forth, "let's see what happens when we do this" self-teaching.Erudy 02:27, 27 January 2012 (UTC)

Upload and Insert Images in one step
Brilliant work! It still lacks some tools, like insert images, videos, audio and documents (pdf, xls, etc) Insert an image or any file from our computer is a complicated process in mediawiki. For common people is almost impossible.

It is so different to the that people get used to in windows and mac applications. In mediawiki you have to click on a link at the sidebar (not in the Editor toolbar) to upload. After that, you have to copy the file name and close the dialog. Then you click in the button to insert. Then you substitute the "File:Example.jpg" by the name previouly copied.

Compare this to the way Wordpress 3.3.1 Editor implemented. They made it so easy to insert images in one single button, one single step! Why don't you use that code? It is well written and it is free. With a few changes you could use that stable and tested code to quickly implement a very useful feature to Visual Editor.

The step by stepUpload Wizard with image copyright may be good for Wikipedia, but is an extension of unnecessary complexity, useless in many other wikis like the one I am developing for fifty thousand users in an intranet environment.

Upload and insert images should be as simple as Wordpress implemented so well in their visual editor.

Please *actively recruit* testers with disabilities
User agent: Mozilla/5.0 (Windows NT 6.0; rv:9.0.1) Gecko/20100101 Firefox/9.0.1

Anytime there's a move to a Visual Anything on the web, I worry about accessibility, in particular for blind people and people disabled by pain like myself, those who find mousing painful.

Everything must be able to be done by keyboard or other methods described by the W3C Web Accessibility Initiative (WAI) or other organizations such as the American Foundation for the Blind:

http://www.afb.org/webaccess.asp

I am too sick to spend much energy here. I'm typing this up without verifying that you don't have such a team in place, which of course could be made of both disabled and currently abled (we all get disabled eventually) people.

Even if you can only recruit abled, sighted mouse-lovers, start there, as long as truly want to learn. It's a good opportunity that way, something to add to the resume about the widening of one's perception and consideration.

Lastly, Courier-type fonts worsen my migraines and occasionally can trigger them over a longer editing session. Please give us the option of editing in some other font that's distinct from that of the article, such as a serif font to contrast with the sans-serif article font.

Thanks for all your hard work. Please don't let us get lost in the scramble. And I truly wish I could be more reliable, but what lets me work on Wikipedia edits is the lack of reporting and deadlines. It's so important to me. It keeps my hand and mind just a little in the editing world I lost over 10 years ago, and with that it keeps me from feeling cut off and useless. Thanks. Geekdiva 03:34, 17 January 2012 (UTC)

Toggle different views, missing features
User agent: Mozilla/5.0 (Windows NT 6.1) AppleWebKit/535.7 (KHTML, like Gecko) Chrome/16.0.912.75 Safari/535.7

Toggling seems to be slow sometimes and this is puzzling. Eventually,graphical feedback about actual state would help.

What I'm missing are tables and GUI for uploading pictures 213.164.88.26 11:50, 17 January 2012 (UTC)

Way to go!
User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:9.0.1) Gecko/20100101 Firefox/9.0.1

This is so important for Wikipedia. Well done. Don't let the haters and nitpickers get you down. That's all! Qwerty0 16:08, 17 January 2012 (UTC)

Macros for editors after they get experienced
User agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.7 (KHTML, like Gecko) Chrome/16.0.912.75 Safari/535.7

The most obvious missing features are images and tables and templates but I guess you know that. Looking very good though.

If you want to keep editors after they get experienced with this the thing to do is to allow them to customize. In particular letting registered editors set up and save macros would give them a strong commitment. People always value things more when they put some effort into. Dmcq 09:55, 18 January 2012 (UTC)

source-editing
User agent: Mozilla/5.0 (Windows NT 6.1; rv:12.0a1) Gecko/20120119 Firefox/12.0a1

the editor needs definitely a source-editing-mode, e.g. for tables. Dänenleo 16:16, 22 January 2012 (UTC)

Sketchy toolbar
Toolbar is so incomplete, there are no Insert image, make a table, refrences, templat, etc... Fabi Fuu 76 00:10, 23 January 2012 (UTC)

Sorry, but there are many bugfixes needed.
User agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1; Trident/4.0; .NET CLR 2.0.50727; .NET CLR 3.0.04506.30; .NET CLR 3.0.04506.648; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729; .NET4.0C; .NET4.0E)

I tested today the new Visual editor, and I saw that there are many bugs. If you click to make a link, then you see that the window is hyaline. Another problem is that you cannot delete a link totally. That are two major problems that need to be solved. 194.31.121.12 11:55, 26 January 2012 (UTC)

Upload images and assign categories?
User agent: Mozilla/5.0 (Windows NT 6.1; rv:9.0.1) Gecko/20100101 Firefox/9.0.1

I really like where this is going, but is their a plan to add those features in the future? 140.190.67.217 17:16, 31 January 2012 (UTC)

Direct editing without heavy editors
User agent: Mozilla/5.0 (Windows NT 6.1; rv:10.0) Gecko/20100101 Firefox/10.0

Great intuitive work with imminent interaction to the written word. Great time-saver. 217.157.144.138 22:29, 31 January 2012 (UTC)

Please consider to implement advanced table editing options
User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0) Gecko/20100101 Firefox/10.0

It's really annoying to edit tables via "hand". Not to mention all the «div» and style=" " options... they drive me crazy! IMO advanced table editing options are a must-have for the new editor. DrLee 14:32, 3 February 2012 (UTC)

Problem in RTL word selection
User agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.7 (KHTML, like Gecko) Chrome/16.0.912.77 Safari/535.7

Hello. I made a test for writing in Arabic. When I doubled click to select one word, the whole line was selected. I wish to enable double click selection for only one word at a time which make it similar to LTR word selection. I hope this problem will be solved in later updates. Ciphers 23:21, 3 February 2012 (UTC)

rte
User agent: Mozilla/5.0 (Windows NT 6.1) AppleWebKit/535.11 (KHTML, like Gecko) Chrome/17.0.963.46 Safari/535.11

rte 92.251.191.15 20:30, 14 February 2012 (UTC)

scroll bar trouble
User agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:10.0.1) Gecko/20100101 Firefox/10.0.1

When I click on the text the insertion point cursor locates to where I clicked, then when I use browser scoll bar to sroll the text where the insertion point is out of the browser window and release the scroll bar the page jumps back to a scroll position that allows the insertion point to be within the window again. Example: I sroll to bottom of a long page of text, click to place the insertion cursor in the middle of a paragraph of text near bottom of page, then I scroll to top of page, release the scroll bar and the page quickly scrolls on its own down to where the insertion cursor is within the window. To get up the page and stay up, I have to move the insertion pointer up. Is this by design? If so, a pop up explaining this interaction design would be helpful when I try to scoll the insertion pointer out of the window. 98.207.154.233 18:43, 15 February 2012 (UTC)

Is this right
We can edit pages without pressing edit button. I need to answer fast.with my best wishes --Argentum (talk) 23:58, 20 February 2012 (UTC)

Side-by-side view: same heading always at same position
User agent: Mozilla/5.0 (Windows NT 5.1; rv:10.0.2) Gecko/20100101 Firefox/10.0.2

Great editor! When I scroll the same document down in side-by-side view, it is scrolled down in both views at once. That is good. However, because the Wiki (old) mode take more space than the direct-editing mode, the headings are no long parallel after a while; at the bottom, the Wiki mode will go on down for a long while after the direct mode has already ended and become whitespace.

I propose that headings should be automatically fixed; that is, if the same paragraph is shorter in one mode, whitespace should be added (only visually) so that the next heading will be at the exact same height in both sides of the window when you scroll.

It may be even better to add whitespace after each paragraph: then each parallel paragraph will always be at the same height, so that you can easily compare the two sides.

However, this should be optional, because sometime you might want to check alignment of pictures and such: perhaps a check box would be good. Cerberus™ (talk) 13:07, 25 February 2012 (UTC)