2017 wikitext editor/Feedback

Post your feedback about using the first iteration of the 2017 wikitext editor as a Beta Feature.

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). Also, while editing to reproduce a problem, please try to append &safemode=1 at the end of the URL; if the problem disappears, you are using a gadget or script that interferes with the editor.

The Editing 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.

We are trying to keep the page tidy by providing links to relevant tasks while closing threads. You can help by adding {{tracked|T######}}. By all means, feel free to re-open a thread if you need to!

See also:

View open developer tasks – Complete workboard – Report a new bug in Phabricator – Join the IRC channel

The New wikieditor is very good. It is intelligent also . I need some essential things missing with old wikieditor.

• The button to add my signature in articles - This is missing. In talk pages click of a button is faster than typing ~ 4 times . Must need a dedicated button on the bar
• Gallery and Reference list are more important than a heirogliph and musical notation
• The single click button to place a redirect is missing. It is a frequently used button in old wikieditor.
• Bold, Italic are frequently used buttons. We need dedicated buttons there also.
• Font problem. On source edit mode the text appear narrow and small - more pressure on eyes.

Find and replace is great. Expecting syntax heighlighting.

--~~~~

There have been many requests for a signature button (for other pages/not for encyclopedia articles), especially for people who write in non-Latin languages. The button is in the Insert menu: Insert > More> Your signature. (On my keyboard, it's faster to type ~~~~ than to take my hands off the keyboard and click any button.) You might be interested in phab:T166494.

There isn't enough space on a computer screen to make everything "important" be in the main toolbar.

I filed a report about the font size at phab:T168092; you may have an e-mail message about that now.

IF you can give some keyboard shortcuts then that will be Ok. I know that there not enough space to place everything.

Request of Shortcuts for

1. Place Signature
2. Place a redirect on the page

Also another requirement is to just rearrange the gallery and Reference before the hieroglyph and musical notation. Is that possible.

I believe that the <references /> item (to make the list) was placed at the end so that it would be easier to find ("all the way down" is easier than "somewhere in the middle").

Does your wiki use galleries frequently?

Yes. We use a lot of image galleries in almost all articles. They make articles more informative and beautiful.

Tracked in Phabricator
Task T169801

I checked 30 articles with Special:Random at mlwiki, and 10% of them had galleries. I've made a general request for the order of items to be reconsidered, and used galleries as an example of what should be considered.

In the case of mlwiki the Special:Random will not give you the real situation. Because lot of stub articles with no image available are there(Malayalam is a small wiki with 50000 articles in total). Most articles translating from English to Malayalam articles are commonly using the images and galleries. The point is we are using galleries, references, redirect more frequently than hieroglyph and musical notation in our wiki.

Yes, I agree that you're using that more than others. I did a proper search just now, and the gallery tag is used at 6% of articles at the Malayam Wikipedia, compared to 4% of articles at the German Wikipedia, 2% of articles at the English Wikipedia, and 0.5% of articles at the English Wikivoyage.

I didn't check, but I suspect that galleries are used at all of these more often than hieroglyphics and musical notation.

sorrjjj ja sam pricam hrvatsii?

You can write in any language you want. Please start a new topic (the white box at the top of 2017 wikitext editor/Feedback).

On the old wikitext editor, clicking a redlinked article that has previously been deleted gives me clickable information at the top including the deletion log for the page and a line I can click that takes me to a page showing deleted edits. On the new editor, clicking a redlink immediately goes into the full editing interface, with the "view X deleted edits" line greyed out and not clickable, and no mention of the deletion log. I can't figure out how to click the "X deleted edits" line without manipulating the URL, and would appreciate being able to see the deletion log.

Sam, are you still seeing this? (You can go to Help:Sample page#World literature and click the red link to test.)

Nope, did the behaviour get changed? :)

I hope so. Unless it's the change that means that I can't hand-edit the URL to avoid the new wikitext mode (which copes very badly on <translate>d pages right now), in which case, I hope that they un-fix it and try a different approach. ;-)

Thanks for the update. If it breaks again, then please come back and let me know.

This is still funky. When I search for a deleted page and click the Redlink I get taken into the page editing interface straight away again.

I can't reproduce this at mw.org today, so I'm hopeful that this means it will be fixed everywhere as soon as the deployment train reaches all the wikis.

This is still fixed at mw.org, and still broken at enwiki and other non-test sites (go to w:en:WP:RA/NS and click any red link to test).

It is not possible to edit a redirect page with this editor, you will infact be redirected to whatever article it points to.

Using chrome, vector wiki skin, this should be easy to reproduce since I wasn't using any scripts. the problem was gone the moment i turned this new editor off in beta settings.

https://en.wikipedia.org/w/index.php?title=Italia&redirect=no&veaction=editsource works for me - I only tried in Safari though. (Where you trying to edit a protected redirect, by chance?)

I didn't think to check, i got anther user to remove the redirect do i could edit the article. acton castle

Возможно ли воспользоваться викификатором в «редакторе вики-текста 2017»?

Нет, невозможно.

И эта тема уже обсуждалась - и здесь, и на странице обсуждения викификатора.

1. (Faviorite in repeat) I [still] hate that it keeps formatting when pasting.
2. I can't copy the article title (to later paste in the article) from the page naem header. It is not "selectable" with the mouse.
3. If I mark some text, then paste something to replace the selected  text, then press ctrl-z, the previously selected text is not selected again
4. Loading the editor is really slow. And if browsing to another tab while it loads, stops the loading until the editor tab is in focus again

1. (which formatting?)
2. I've added this to https://phabricator.wikimedia.org/T156047 for now.
3. I can. Details of your configuration, please?
4. I tried with multiple articles, including 3 featured articles on en.wp, and all of them were already loaded by the time I got back to the tab. Any particular pages this may be happening on?

1. Wikicode formatting. Like if I copy cope from a 'code' or 'pre'-block (such as the examples with parameters in template documentations) I get it 'nowiki-fied. And copying words from other articles includes links and stuff. As a long-time user of the old editor, this is completely unexpected behavior and personally not wanted.
2. Thanks
3. Will do. when i get home from the gym in half an hour.
4. See below. It happens on all pages. Same as the Phab ticket below.

For 1, you can always use CTRL+SHIFT+V to force paste plain text though. Conversation continues at https://phabricator.wikimedia.org/T153315.

(Which FWIW was resolved.)

Update: Expect some improvements when pasting things from the <pre> block soon. But if you're pasting bold-face text, it's still going to be bold-face text, unless you force your web browser to paste plain text.

Re #4, see https://www.youtube.com/watch?v=YRprzyIbydU

#4 is reported here: https://phabricator.wikimedia.org/T154329

Josve05a, could you remind me which browser you're using? I see #4 in Firefox sometimes, but I'm not sure that I'm seeing it in Safari (although in Safari, I see an analogous behavior with Google Hangouts, which is very annoying to me: open a hangout for a meeting, go to another tab, wonder why no one else is showing up, go back and discover that the meeting started, but the browser tab never noticed).

I'm using chrome on a chromebook with chromeOS.

On #3, it's working for me in Firefox and Safari.

@Josve05a, Can you try in incognito, from another browser, etc.?

Hello to all and to all !

Further to the announcement of the community to delete(eliminate) our expensive and soft bar(helm) of tool for the benefit of an other one at present in stupid man in the mode Wikitexte, I take advantage of it to make some complaints which(who) seems to me justified:

* We ask for the compatibility of the gadget DotsSyntaxHighlighter the new mode of wikitexte

* We ask for the compatibility of the gadget Quick Preview the new mode of wikitexte

* We ask for the institution of most of the features of ForceMonobookToolbar the new bar(helm) of tool of the new mode of wikitexte

Delete(Eliminate) our good old bar(helm) of tool to proceed to the transition on the long term for the benefit of the new mode of wikitexte : why not?! But we delete(eliminate) something so important for us the old dinosaurs of Wikipedia with nothing in return! I hope that these complaints shall not go unheeded!

I'm not sure which project you're talking about. You may be looking for Contributors/Projects/Accessible editing buttons or Contributors/Projects/Removal of the 2006 wikitext editor or another project.

It's okay to write in French on this wiki. Also, please give me links to these gadgets. They look useful. :-)

This is the NewEditor Feedback page, and their phrase "new mode of wikitexte" clearly refers to this project. The three bullet points are clearly complaining about how NewEditor breaks all wikitext editor gadgets and scripts. (I deliberately didn't include that point in my RFC to fix the NewEditor, but that point would be included in an RFC to roll it back from our end.)

I can pretty well interpret the rest too. They're definitely making the connection that you're removing the wikitext editor to push VisualEditor. They would support a new wikitext editor if it were an improvement, but you're removing our valuable flexible tools and the NewEditor gives zero benefit in exchange. They end saying not to ignore the community's complaints.

I noted the poster's use of "We" rather than "I". I did some searching on French Wikipedia. I'm not sure which specific discussion they were referring to, but yes, I found other people on FrWiki objecting to the NewEditor. Unsurprisingly, they were complaining about preview and that the new editor was unusably slow. On the latter point, one person particularly commented about developers living in a California-bubble, saying that people in the rest of the word don't have high power computers capable of running it. I think the NewEditor wouldn't work for them at all.

I'm pretty sure "dinosaur" was sarcastic mocking of WMF disdain for experienced editors. It's possible that their use of "stupid" was sarcastically mocking the WMF's view of VisualEditor for new users. I admit that my basis for interpretation there is a bit thin, however those particular words appear unlikely to be stray translation glitches and that interpretation fits the general theme of the message.

Alsee, at the moment, the community at the French Wikipedia is primarily concerned about the plan to truly "delete" the 2006 wikitext editor, and to replace it with (literally) "nothing in return" (i.e., no toolbar at all).

As you have been told many times, the devs are not "removing the wikitext editor to push VisualEditor". They aren't removing wikitext, and they have promised that it will be possible to edit wikitext without using either VisualEditor (any part of it, including its new wikitext mode) or Javascript for the foreseeable future.

I have therefore asked Menthe to clarify his comment.

(As for updating gadgets: Gadgets and other user scripts are entirely the responsibility of the users who created them, and they are absolutely free to updated their scripts whenever they want, including to make them work inside either or both modes of VisualEditor. They don't need the WMF's permission to do that.)

Regular page moves works, but when the target already has a page and I click on the button to delete the target page to make space for the page I want to move... The page editor opens up, making me unable to execute the move without shutting the 2017-editor off.

Windows 7, Google Chrome, MonoBook.

Tracked in Phabricator
Task T167832

(My user page on en.WP discusses my limitations to some degree.)

Since the 1990s I've seen many tools migrate from text-based interfaces to graphical ones, and not always with good results for various sets of users with various disabilities. I've just used this editor, and it did not surprise me. It significantly increased the amount of mouse clicks I was forced to use to complete a task.

(Side note: Clicking Publish... to get to Preview... is right up there in awkwardness with Windows' Start > Shut Down.)

One of the reasons I wasn't surprised was because of the careless usurpation of Alt-Shift-V. Even though as of the time of this post it still is in the tooltip on en.WP if you hover over the Show changes button, the shortcut's function is now to switch you to the Visual Editor.

There is at least one bug about this, but if you look at my en.WP user page, you might get some understanding of why, when I found it had been closed or had been given some such status, I didn't try to figure out how reopen the issue. I have to do what I can, when I can. I was discouraged and out of when-I-can.

So now I have to use what hotkeys I can simply to get to that button's location before wasting an incrementally pain-filled mouse click on it, and I use that view often to make sure I don't upload the wrong thing after, say, passing out or a stillsdisease.org fever spike. And right before I click, I get irritated by a tooltip that still shows me how I used to check my [V]ersion before saving it by comparing it with the previous [V]ersion.

It's like a poorly-formed curb cut: you don't notice it's a problem unless you have to push overly hard against it to move on when it's supposed to be there to help you move on in the first place.

Thank you for all your hard work in general, your patience with my irritated tone in this post, and your consideration of how to make this tool in particular less mouse-click dependent for those of us who are rodent-impaired. I'd consider help on the Alt-Shift-V problem a bonus.

I will try to take notes the next time I use the 2017 Wikitext Editor so the bulk of my feedback's details on this page can be on what this page is actually about. Heh!

Just a personal note as a volunteer who often tries to fix and evaluate these kinds of accessibility problems.

1: You can always mail me with whatever problem you have and I will make sure we at least have a ticket for it, an analysis of the problem and an idea of what would be required to fix it. The actual fix might take a while.

2: "how to make this tool in particular less mouse-click dependent" We strive for all tools to be fully keyboard accessible, but often we miss something, because we don't rely on this accessibility ourselves. Please DO tell us, it is important to us.

3: More mouse clicks are going to be needed, because the software gains ever more features and complexity and we can't put all that in a single window of course. Again, we try to make everything keyboard accessible, if you need something, please let us know either by mail or in phabricator.

Hi Geekdiva,

Thanks for this note. I've filed a bug about the alt-shift-v problem.

For visual mode, I think that you might want to take a look at the keyboard shortcuts. They're at VisualEditor/Keyboard shortcuts – no, don't reach for the mouse: if you can't tab to the link in your browser, then Alt+⇧ Shift+f (or your usual meta keys + f; it's Ctrl+⌥ Option+f on my Mac) should take you to the search box, and then you can type the name without another mouse click.

There are also a few undocumented shortcuts in the visual mode that might interest you: {{ opens the template dialog, and [[ opens the link tool, which is handy for both avoiding cut-and-paste maneuvers and perhaps a little easier to remember for long-time editors than the official version, which is Control+k (for PCs; Command-K for Macs). And the reason that meta-k is worth mentioning is because there's a new shortcut for the citation dialog, which is Control+⇧ Shift+K (⌘ Command+⇧ Shift+K on a Mac).

I'd be happy to hear more from you about whatever you want to share, from the bad curb cut to the minor paper cut.

P.S. This message, including formatting, was typed in visual mode, entirely from the keyboard (except that I'll have to use the trackpad to click the reply button), because I share your POV on the subject. It's not possible to do everything without a mouse/pointer here, but it's pretty close.  :-)

Tracked in Phabricator
Task T166494 Stalled

The current wikitext editor seems to be missing an option to easily add signature to talk page discussions. It would be nice if it was enabled in some way. Two possibilities are:

1. Keyboard shortcut
2. Option in menu bar

Expecting one soon!

The keyboard shortcut is ~~~~.

The option in the menu bar is halfway down in the Insert menu: Insert > More > Your signature.

Yeah, but when I was mentioning about signature I had the signature added by the old wikitext editor (- -~~~~) in mind. I guess a keyboard signature to add would be useful for users who are in a situation to sign often. (Obviously, this isn't required if Flow is used in places requiring user interaction)

Regarding the option, it would be better to show it more explicitly as a way of inducing the user to sign their posts in Talk pages and other pages where signature is required.

But for Me. I want to switch to engish keyboard layout from Malayalam first to get the ~ character. then press ~ four times is the only way. If i get a keyboard shotcut like Alt+Shift+S or something like that for this thing then it is a way better . If I am typing in english pressing a ~ four times is not a big deal. But changing the keyboard layout from Malayalam to english is a different scenario. Hope you understand.

Now my keyboard short cut is

Super+Space > Select English > ~ four times > Super+Space > Select Malayalam

What I expecting is

Alt+Shift+Somekey

No changing of keyboard layout Included.

Also I think lot of non latin people face this problem.

That's right. Other language editors would be a great audience of this shortcut.

There needs to be a "link to another wiki" tool that would add the proper prefix to the link (e.g. Wiktionary -> wikt, or even French Wiktionary: wikt:fr:).

Right now it is like the good old wiki code: you need to know and write the right prefix yourself.

Another small issue: Wiktionaries are case sensitive, so the capitalization of the first letter also has to be fixed manually when creating such a link (highlight text > make link). And even if I do change it, the final link has its prefix capitalized too (sure the link works but it's not a good habit).

If you just paste an external link to another wiki it will get converted to the correct notation.

One related bug has been solved: phab:T166593.

But you may be affected by phab:T133535 or another problem.