2017 wikitext editor/Feedback

About this board

Post your feedback about using the first iteration of the 2017 wikitext editor as a Beta Feature. While you can disable it by unchecking the New wikitext mode checkbox in your Preferences (Beta tab), 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. You can learn how to structure well your submission.

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.

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 PhabricatorJoin the IRC channel

Edit notice link disappears

1 (talkcontribs)

When I enable "New Wikitext Mode" the red link "Page notice" that allows adding edit notices disappears. I'm an admin if that makes a difference. I tested it with the old and new Vector skins. ~~~~

Reply to "Edit notice link disappears"

Doesn't automatically expand when collapsed sidebar in New Vector

CactiStaccingCrane (talkcontribs)

When I collapse the sidebar in New Vector, the edit form didn't automatically expand to fill the white space. The same thing happens on VisualEditor as well.

Reply to "Doesn't automatically expand when collapsed sidebar in New Vector"
TadejM (talkcontribs)

Hello. I'd like to report a bug when using 'New wikitext mode' in the English Wikipedia. The lines of wikitext overlap with each other and also with the editing interface when I am editing on mobile with the desktop view. I'm using Chrome in Android (Samsung phone), but toggle the desktop view.

Whatamidoing (WMF) (talkcontribs)

Is the text colorful? If so, the problem is in CodeMirror (the syntax highlighting software). You can turn it off in the "hamburger" menu (three lines near the big blue Publish button).

TadejM (talkcontribs)

Thank you. I've figured out wikEd was the cause. I've turned it off, but this is less than an optimal solution. Anyway, I suppose it was causing other trouble as well.

TadejM (talkcontribs)

It turned out wikEd was not the true problem since the problem persists but the page displays correctly if I reload it on mobile... I will let you know as soon as I figure this out. --TadejM (talk) 21:11, 17 January 2023 (UTC)

TadejM (talkcontribs)

I have not figured out the exact cause. None of the gadgets or beta functions seem to resolve the issue. I'm attaching the link to a screenshot. As said, when I reload the page, it displays correctly. I'm using a Samsung Galaxy S21 phone with Android 13 and opening the file in Chrome 108 (desktop view).

TadejM (talkcontribs)

After disabling all gadgets and removing all custom css and js, I've now found that the issue is strictly caused by the option 'New wikitext mode' (i.e. 2017 wikitext editor) under Preferences/Beta features. It appears when I enable this mode and disappears when I disable it. I tested this in the English Wikipedia.

(In addition, wikEd does not work with this mode. I guess though that this must be resolved by its developer.)

TadejM (talkcontribs)

In addition, the responsiveContent gadget caused me problems when working on desktop. I had to disable it since when it was enabled, I was unable to correctly select wikisyntax. It is described as "Improved appearance for mobile, narrow and wide screens". I don't know if it caused any problems on mobile. Blank space was selected and when I tried to delete it, the wikitext was deleted instead.

Whatamidoing (WMF) (talkcontribs)

TheDJ will want to know about the gadget.

What happens if you go to the "hamburger" (three lines) menu and turn off syntax highlighting?

TadejM (talkcontribs)

I left TheDJ a message on his talk page. The issue only occurs when syntax highlighting is enabled. Otherwise, everything seems to work fine.

Reply to "Garbled wikitext"
Aaron Liu (talkcontribs)

The new VE isn't as good as the "2010" editor as it currently stands. The load time is way longer than the normal editor. The realtime preview feature doesn't work though I guess this is something else. The commonly used characters at the bottom aren't there. A lot of integral toolbar functions such as syntax highlighting appear to be missing. A lot of features from VE appear to be missing, such as editing templates using the vetemplatewizard, so the only advantages this appears to provide are the cite tool and the new buchered toolbar. Just my thoughts, I appreciate the entire project behind this.

Reply to "My general issues"
Skalman (talkcontribs)

Hi, I'm creating a gadget for improved source editing. Are there any hooks that I can use?

So far, I am aware of the following ways to edit wikitext:

  • Traditional <textarea> (action=edit)
    • Hook: wikipage.editform
    • Edit with: $("#wpTextbox1")
  • Syntax highlighting with CodeMirror (action=edit)
    • Hook: ext.CodeMirror.switch
    • Edit with: elementFromHook.CodeMirror
  • 2017 wikitext editor (veaction=editsource)
    • Hook: ???
    • Edit with: $(".ve-ce-documentNode") - do you have anything more exact?

Also, is there a good way and place to show warnings that the user will see before saving?

Nux (talkcontribs)

Check this out for 2017: VisualEditor/Gadgets#User's position in the model. Seems to work fine for inserting text. Note that you can use `new ve.Range( 0 )` to insert at the beginning of the text.

The hook seems to be `ve.wikitextInteractive`, but haven't tested this.

Skalman (talkcontribs)

Thanks for the pointers, Nux. That link was very helpful!

Preview button

Summary last edited by Aron Manning 20:04, 3 June 2019 3 years ago

From [en:WP:KB]: on Windows, Chrome hold Alt+ Shift or Alt+Control+ Shift or Alt, then press p for preview, or v for changes (diff). The modifier key can be different per browser. Note: neither of these works for me in Visual Editor on Chrome, but it's worth a try. - Aron

From the Phab [Task T153306]: Alt+ Shift + p or + v will take you to preview/diff. - Aron

On Mac, it's Control+ Option+p and Ctrl+ Option+v for preview and diff. - Whatamidoing

Lesendes Okapi (talkcontribs)

Please include a "preview" button next to the "save changes" ("Änderungen veröffentlichen")-button! It's nice that the program kindly reminds me to do so after I hit the save-button and for newbies, which would probably not use the preview-button at all it is fine, but as a user who is used to the old editor I got panic as it looked like I had only the option to save the changes without a previev :) --~~~~

Erentar2002 (talkcontribs)

Yeah, a preview button before the "save changes" button would be nice. I would really like not to have to click save changes to preview my changes

Paucabot (talkcontribs)

I agree.

Whatamidoing (WMF) (talkcontribs)

I have found it worthwhile to learn the Keyboard shortcuts for this command. They are the same ones that you use in the older wikitext editors.

Lesendes Okapi (talkcontribs)

Maybe I am blind but I can't find a shortcut for preview in the overview you linked above :(

Can you write it here?

Whatamidoing (WMF) (talkcontribs)

Oh, my fault! You need the main list at m:Help:Keyboard shortcuts, not the extra handful added to VisualEditor.

On my Mac, it's Control+ Option+p and Ctrl+ Option+v for preview and diff. The meta keys are different in Windows (and sometimes by web browser).

Whatamidoing (WMF) (talkcontribs)

@Aron Manning, you should feel free to post your own content in your own message.  :-)

For everyone else, Aron has added the Windows keyboard shortcuts:

From the Phab Task T153306: Alt+ Shift+ p or + v will take you to preview/diff.

From WP:KB: on Win, Chrome hold Altor Alt+ Shiftor Alt+Control+ Shift, then press pfor preview, or vfor changes (diff). Note: neither of these works for me in Visual Editor. - Aron

Aron Manning (talkcontribs)

@Whatamidoing (WMF)

 :-) Did not intend to ruin your comment. I hardly noticed your updated link down here... Can I suggest you to update the link in your first comment, and copy the shortcuts there? Feel free to copy the chrome shortcuts too. It would have been helpful to me, thus I believe it will be helpful to others. Thanks.

Aron Manning (talkcontribs)

Ping to move discussion to top. More important than testing copy-paste.

Saper (talkcontribs)

This was reported on plwiki technical noticeboard, too: https://pl.wikipedia.org/w/index.php?title=Wikipedia:Kawiarenka/Kwestie_techniczne&oldid=57207917#Powr%C3%B3t_do_edytowania_(Priority_low)

The editing flow is very confusing to me, and shortcuts are not a solution to the problem.

I personally prefer edit -> preview -> edit -> preview -> edit -> preview -> submit flow, and the submit button should be not the first one to reach. Also the preview should be smoothly integrated in the editing flow and not be an extra thing that pops up with an animation. This way no user will feel like using it.

For normal editing I am pretty happy with old wiki editor and the live preview feature (it has its issues but it works very snappy).

This feature forces me to do an "edit -> submit -> maybe preview -> have a look -> go back -> edit flow" which is cumbersome and unnatural.

Ivanics (talkcontribs)

Yes, the best flow would be: edit -> preview -> submit (or preview again)

HLHJ (talkcontribs)

I also prefer edit -> preview -> edit -> preview -> edit -> preview -> submit, and I preferred it much more strongly as an uncertain new editor; the "Preview" button was very reassuring. I suspect I'd never have hit "submit" without that reassurance. Keyboard shortcuts are nice, but they are not the first interface the new user sees. Honestly even a lot of experienced editors don't know they exit (I know they exist, but they don't work for me, not sure why).

Add apparently they are deprecated? "Usage of access keys is currently discouraged in the online contents and applications". Because they conflict with screenreaders. This is daft. Wikipedia is, according to several vision-impaired people, pretty much inaccessible with most screenreaders, because instead of having a background tone or change in voice timbre for links, most screenreaders read the link targets aloud. Most WP articles have so many wikilinks that listening to them on such a system is insanely annoying. Even tech-savvy blind people often just do without rather than bother with it. WP needs an interface for vision-impaired users, and a related one for users with low or no literacy, especially as ownership of net-enabled phones by illiterate people increases.

Whatamidoing (WMF) (talkcontribs)

It looks like that was added in 2010 by Dodoïste. Looking at the whole section, it says that WCAG "abandoned" them and ATAG required them, and the editor believed that Wikipedia should comply with both. However, I'm not sure that's a complete description of WCAG back then; in particular, WCAG 2 was discouraging "character key shortcuts", which do not use any modifier keys. (The difference is whether you type Control+f or just f. If it's just f, then it's easy to accidentally trigger it.)

The 2010 summary looks out of date to me, since the current rules say that any HTML element may have an access key (which must use at least one modifier key, and normally follows the conventional modifier keys for that platform).

HLHJ (talkcontribs)

I've figured out why they weren't working for me, a clash with my attempts at multilingual typing configuration. Entirely on my computer, nothing to do with Mediawiki. I don't know enough to update that page, but I'll template it as out-of-date.

Reply to "Preview button"

Problems with copypasting and clipboard from the latest update

Summary by Whatamidoing (WMF)
Solidest (talkcontribs)

Having the problems with the clipboard and some difficulties with copy-paste in code mode, which are started somewhere around 1,5 weeks ago.

  • The clipboard does not work between browser tabs. It is as if the pages have their own built-in clipboard
  • Copying text into it now happens by any text highlighting. In doing so, copied lines often cut off the first or last character in the line.
  • The copying works in some random way, each time chunks of random text are copied from the current cursor position. Even if I did not highlight text or press Ctrl+C
  • Ctrl+X does not work as it should, but deletes the text completely and copies all subsequent text

All this only happens in the code editor when "New wikitext mode" is enabled. I've tried disabling all scripts and resetting wikipedia settings - it doesn't help. Problems appear for me in both in ruwiki and enwiki where I work and also both in Firefox and Chrome. There are no such problems in the standard code editor or any other sites.

Whatamidoing (WMF) (talkcontribs)

Do you have the colorful CodeMirror syntax highlighting turned on?

Solidest (talkcontribs)


Solidest (talkcontribs)

But the bug occurs even when markup is switched off. Although sometimes it does not appear immediately, but only after some work with the page code (mostly after several iterations of ctrl+x and ctrl+c). And then literally the only proper way to make a cut-paste work is by selecting and dragging text with the cursor to the needed space... This makes the visual editor simply unusable.

Chelsdog (talkcontribs)

I'm facing the same issue. Have you figured out the solution?

Solidest (talkcontribs)

Nope. Only keep finding even stranger cases of occurrence. For example if you open a new page - press edit code - select all, cut and paste to the same page - then all code will be written in one line without line breaks, and sometimes the highlighting continues to act as with a "shadow" of the original version of the page, selecting empty line formatting behind the current text. I think it's a bug within the visual editor, which started at the end of July.

Whatamidoing (WMF) (talkcontribs)

What's your operating system (Windows, Linux, Mac, etc.)?

Do you use the middle mouse button for copying and pasting? (See Topic:Wzjvn2kn8sxsltw6.)

Do you have problems with text getting "scrambled"? For example, you're typing at the end of a sentence, but the letters are added to the middle?

Solidest (talkcontribs)


Not using middle mouse.

No, there are no problems with normal typing as far as I remember, only copying and pasting.

Reply to "Problems with copypasting and clipboard from the latest update"

Links for deleted revisions and logs are unusable

Summary by Whatamidoing (WMF)
Huñvreüs (talkcontribs)


As a sysop, when I try to re-create a previously deleted page using the 2017 editor, the following text is displayed: View or undelete one deleted edit? (view logs for this page | view abuse log), but it is disabled, I cannot click on any of the links. This issue does not arise when I use the classic editor.

Nick Moyes (talkcontribs)

Yes, I observe this, too. I want to view (as an admin) someones deleted page, I click that redlink and it tries to create a new page in Visual Editor, and even if I clear the templated message, the 'view/undelete' link does not function. I have to select 'Create Source' before the view/undelete link is functions.

Not working with flood

Summary by Whatamidoing (WMF)
Ferien (talkcontribs)

On simplewiki, my home wiki, I often make lots of minor changes in a short amount of time and when I do so, I use flood, where the changes I make are hidden from recent changes through a "flooder" user right. Edits made when I have flood on are marked as bot edits, but in 2017 wikitext editor, the edits still appear in recent changes for some reason, and I'm not sure why.

Whatamidoing (WMF) (talkcontribs)

That's strange. Does the same thing happen with edits you make in the visual editor?

Ferien (talkcontribs)

I'm not sure, I haven't tried yet. I will test that when I can.

Ferien (talkcontribs)

@Whatamidoing (WMF) I have just tested it in visual editor. Yes, edits made in visual editor aren't marked as bot edits either

Whatamidoing (WMF) (talkcontribs)

Quiddity (WMF), do you still have flood rights somewhere? Could you try to reproduce this problem in VE for me?

Quiddity (WMF) (talkcontribs)

Confirmed (with 'bot' usergroup, but functionally the same) on officewiki.

I made an edit with the 2010-editor and it was correctly marked as 'b' in RecentChanges. I made another edit with VE and it wasn't.

Searching phab, it appears this is already filed as phab:T284855.

Whatamidoing (WMF) (talkcontribs)

Thanks, Quiddity. From the looks of the Phab tasks, the answer is buried somewhere in the interaction between the 2017WTE and the API. Unfortunately, my best guess is "won't be fixed any time soon".

Reply to "Not working with flood"

Can't switch to visual editor

Beland (talkcontribs)

On English Wikipedia, after enabling this beta feature, I tried editing a whole article, and section of an article, user page, and talk page. The option to switch to visual editing was greyed out and in all cases I could not click on it.

BTW, is this project dead, or is this still planning on being deployed some day?

Whatamidoing (WMF) (talkcontribs)

Deployment (default-off) could have happened a couple of years ago. I don't know when it will happen. Hopefully phab:T202921 will happen first.

I can't reproduce this problem. The visual editor is disabled on talk pages, so that's expected. But you should be able to switch in articles and on your user page. Is this still a problem for you? Is it a problem on this wiki? You can use User:Whatamidoing (WMF)/Sandbox to test it here.

Beland (talkcontribs)

The switching to visual editing is working for me at User:Whatamidoing (WMF)/Sandbox but not at e.g. w:Earth. I tried turning off all the other beta features, and returning to the Vector 2010 skin, but those didn't make a difference. Perhaps it is one of the non-default gadgets I have enabled in my preferences?

Whatamidoing (WMF) (talkcontribs)
Beland (talkcontribs)

I'm getting some very strange behavior. I went to https://en.wikipedia.org/wiki/Earth?veaction=edit&safemode=1 and was able to switch between. I then went to https://en.wikipedia.org/wiki/Earth and tried disabling non-default gadgets a few at a time to figure out which was the problem, to no effect. Then I tried disabling all the default gadgets, and even after re-enabling those, I can't get the new wikitext editor at all from https://en.wikipedia.org/wiki/Earth nor https://en.wikipedia.org/wiki/Earth?safemode=1 even though the beta feature is enabled in my preferences and I've shift+reloaded. And I don't see any way to get to the visual editor, either. Perhaps this is because I normally don't use the visual editor?

I can still get the beta editor and switch back and forth if I go directly to https://en.wikipedia.org/wiki/Earth?veaction=edit&safemode=1

Whatamidoing (WMF) (talkcontribs)
Beland (talkcontribs)

Just tried that; symptoms are the same. -- Beland (talk) 03:08, 28 May 2022 (UTC)

Whatamidoing (WMF) (talkcontribs)

Just a note to say that I haven't forgotten you. I'm just not sure what the problem is. If it works in safemode, then it's some sort of gadget or user script. Help:Locating broken scripts or a request for help at w:en:WP:VPT might be your best bets.

Reply to "Can't switch to visual editor"