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

Diego Moya (talkcontribs)

I've enabled the New wikitext mode on Beta preferences, and it makes the "Edit source" mode unusable from Firefox on Android. The caret is shown at a different point to where the text is inserted (see images below). The same problem appears on Firefox Beta for Android.

I tried to edit article Strategies for Engineered Negligible Senescence, section Scientific controversy, and the following happens:

1) I tap in front of "Science fact..."

Clicking on a point in text

2) The window scrolls automatically to the top of the text area.

The editor field scrolls to the top

3) I scroll down to the paragraph I want to edit. The caret is shown where I tapped the screen (as seen in Image 1). But when I type "Example text", the text is entered here instead:

The typed text is placed at a different point of the text field

The interface has problems also when selecting text by long-pressing and dragging the finger; the drawn selection box is not vertically aligned with the text.

It is possible that the extension is interacting with some of my scripts at commons.js or commons.css for the old editor.

Whatamidoing (WMF) (talkcontribs)

Sorry for missing your post earlier, Diego. Does that problem go away if you turn off syntax highlighting?

Reply to "Unusable on Firefox Mobile"
SSSB (talkcontribs)


I'm not sure if this is something that is relevant, but a heads up that some scripts don't work when this is enabled. Specifically, this one.

Jdforrester (WMF) (talkcontribs)

Hey there,

Changing user scripts and community gadgets to work with the 2017 editor is the responsibility of the owners of that code. In that particular case, have you asked Ohconfucius? It might be pretty trivial, or it might be a fair bit of work for them to fix their code to work in both editors.

Reply to "Some scripts don't work"

Be able to alternate between editors

Berrely (talkcontribs)

I really do love the 2017 wikitext editor, I really do, but a lot of my scripts only work on the default one, and it is quite frustrating having to constantly go to the beta panel and switch it on and off. Is there a quicker way to switch editors than this?

Whatamidoing (WMF) (talkcontribs)

When I need to invoke one of the older wikitext editors, I hand-edit the URL to say &action=submit instead of &action=edit or &veaction=edit. This is not exactly convenient, but it is 100% reliable and quicker than changing preferences.

Berrely (talkcontribs)

@Chlod wrote a neat bookmarklet that does this automatically, for anyone that needs it:

javascript:void function(){javascript:(()=>{if("en.wikipedia.org"==window.location.hostname){const a=new URLSearchParams(window.location.search);a.has("action")%3F"edit"==a.get("action")%26%26a.set("action","submit"):a.set("action","submit"),window.location.search=a.toString()}})()}();
Chlod (talkcontribs)

@Berrely, the script has a few issues from minification (namely, it won't run due to a syntax error in the first section), so use this instead:

javascript:(()=>{if(window.location.hostname!="en.wikipedia.org")return;const params = new URLSearchParams(window.location.search);if(params.get("action")==="submit")params.set("action","edit");else params.set("action","submit");window.location.search=params.toString();})();
Pandakekok9 (talkcontribs)

How do I make the script work for both English Wikipedia and Wikimedia Commons? I'm not that experienced in JavaScript. Thanks!

Chlod (talkcontribs)

Here's an approach that will make it work on all MediaWiki wikis.

javascript:(()=>{if(mw == null)return;const params = new URLSearchParams(window.location.search);if(params.get("action")==="submit")params.set("action","edit");else params.set("action","submit");window.location.search=params.toString();})();
Sportzpikachu (talkcontribs)

@Pandakekok9: you can use this modified version:

javascript:mw!=null?void((params=new URLSearchParams(window.location.search)).get("action")==="submit"?params.set("action","edit"):params.set("action","submit"),window.location.search=params.toString()):void 0)
Pandakekok9 (talkcontribs)
Chlod (talkcontribs)

Sportz's version is much more compact, and is executed with just a single JavaScript statement. There's no difference other than the 31-character gap.

Pandakekok9 (talkcontribs)

@Sportzpikachu's version for some reason doesn't work on Pale Moon 28.17.0. It's attempting to contact "intake-logging.wikimedia.org" when I try to use it.

Reply to "Be able to alternate between editors"

Citation error due to date format

Femkemilene (talkcontribs)
Reply to "Citation error due to date format"
Technob105 (talkcontribs)
MBq (talkcontribs)

Agreed, it’s viscous on slow hardware.

Reply to "Vraiment pas pratique"
LaMagiaaa (talkcontribs)

The Template used shows all template in the page. But when I edit some section, I more hope it shows me only the template used in that section. Could you make the template used in a section highlightly or just only show those template?

Reply to "Template used"

Suggestion: Additional conveniences for wikitext mode

EnronEvolved (talkcontribs)

Long citation templates and tables can get in the way of reading the article text in source code view, so the ability to fold templates would be a useful addition to the new editor.

Reply to "Suggestion: Additional conveniences for wikitext mode"

preview link may wrong in Wiki with variants

LaMagiaaa (talkcontribs)

Edit in Wiki with variants and make a link in the non-transfer mark (this one: -{}-, I don't know the official name), like -{[[link]]}-, and when the URL is like xxx/w/index.php?... the link is to /w/link, a Page-not-found page.

I don't think it matters: Windows 10, Chrome 88.0.4324.150, Timeless


Reply to "preview link may wrong in Wiki with variants"
Xhs44444100 (talkcontribs)
  • Web browser: Microsoft Edge (Chromium) ;
  • Operating system: Windows 10 版本1909 ;
  • Wiki skin: Vector.

今天使用2017 wikitext editor时,光标总是无法对齐文字。

Air7538 (talkcontribs)


Reply to "光标无法对齐文字"
Some1 (talkcontribs)

My only complaint about the 2017 wikitext editor is that the 'Show preview' function takes up the whole height and width of my monitor screen; I don't need the preview to be that large.

Is it possible to have the 2017 wikitext editor's 'Show preview' function/preview page be exactly similar to the default/non-visual/non-2017 wikitext editor one?

Other than that, the 2017 wikitext editor is pretty great!

ESanders (WMF) (talkcontribs)
Reply to "'Show preview' function"