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

preview link may wrong in Wiki with variants

3
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

Thanks

Whatamidoing (WMF) (talkcontribs)

Sorry about the late reply. Is this problem happening in Chinese? Is it still happening? (Every language that uses variant scripts has its own, separate set of problems.)

LaMagiaaa (talkcontribs)

It is happening in Chinese. (And I have choiced some language uses variant wikis, it is also happening. So I think this is a common problem of variant languages)

Just like I said, edit some page URL liked "zh.wikipedia.org/w/index.php?..." and using -{}-, for example -{[[link]]}-, this link will go /w/Link on preview page.

Reply to "preview link may wrong in Wiki with variants"

Previewing is annoying and sometimes doesn't work properly

3
Nixinova (talkcontribs)

In order to preview a page with the new editor, you have to first click the publish button, then wait for the summary box to appear, then click preview -- extremely annoying when I want to iterate a specific change. At least on mobile it shows the preview by default.

Additionally, templates like Wikipedia:Template:Graph:Chart just straight up don't work, and don't work on mobile either. I had to disable this just to edit pages like Wikipedia:Opinion polling for the next New Zealand general election.

What I would primarily like to see is a preview button directly next to the publish button. Figuring out a way to get the graph template appearing would be a bonus as well.

Tol (talkcontribs)

I agree; preview should not be under publish (VisualEditor too). Another annoying effect of this is that one cannot preview if no changes have been made (the publish button is disabled until a change has been made).

Nixinova (talkcontribs)

The trick I use to preview a null edit on mobile is just to add a space and remove a space, preview button appears.

Reply to "Previewing is annoying and sometimes doesn't work properly"

Some problems

1
Summary by Whatamidoing (WMF)
195.110.77.193 (talkcontribs)

I tried the beta option on hewiki and had some problems with it:

  • I could not figure out how to preview the result. With current editor I occasionally press "Preview" and see the result (above my test). Mostly useful on shorter texts. Here I have to go through Publish Changes => Preview. And I don't have my text and the preview in the same screen. Show stopper.
  • considered switching to the visual editor as a sort-of preview. But when I edit one section, switch to visual editor and switch back, I'm editing the whole document.

So right now I disabled the beta option.

Reply to "Some problems"

光标无法对齐文字

6
Summary by Tol

Translation: Cursor does not align with text

Xhs44444100 (talkcontribs)
  • Web browser: Microsoft Edge (Chromium) ;
  • Operating system: Windows 10 版本1909 ;
  • Wiki skin: Vector.

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

Air7538 (talkcontribs)

原来对不齐文字是广泛发生的问题,。,

Whatamidoing (WMF) (talkcontribs)

Do you use the colorful syntax highlighting (CodeMirror)?

50829! (talkcontribs)

YES.I have the same problem, too.

Whatamidoing (WMF) (talkcontribs)

Did you have this problem last year, or is it fairly new?

Whatamidoing (WMF) (talkcontribs)

Another question: Is the cursor always misaligned by the same amount (e.g., wrong by 5 mm), or does it change (e.g., wrong by 5 mm at the start of the line and wrong by 1 cm at the end of the line)?

Reply to "光标无法对齐文字"

Suggestion: Additional conveniences for wikitext mode

5
Summary by Whatamidoing (WMF)
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.

Whatamidoing (WMF) (talkcontribs)
FMM-1992 (talkcontribs)
FMM-1992 (talkcontribs)
Whatamidoing (WMF) (talkcontribs)

I don't think that any team plans to work on CodeMirror during the next year. My impression is that it is a lot of work for a small benefit.

Reply to "Suggestion: Additional conveniences for wikitext mode"

Citation error due to date format

2
Femkemilene (talkcontribs)
Whatamidoing (WMF) (talkcontribs)

The English Wikipedia has decided to reject this class of ISO standards-compliant dates. I find it annoying, too.

Years ago, I heard editors justify this rule because of the fear was that future editors would not be able to tell whether 2001-02 meant two years (2001–2002) or a year and month (February 2001). However, there is no possibility of confusion any source after 2012, and only a tiny fraction of dates from 2000–2011 would be potentially confusing and not banned by the English Wikipedia's MOS.

In the last discussion I had on this, we couldn't even agree about whether the MOS rule applies to what's typed in the wikitext vs what's shown to readers. (For example: So long as the reader sees July 2021, does it matter if I typed |iso-date=2021-07 in wikitext?)

Reply to "Citation error due to date format"

Edit summary and suggestion for Syntax highlighter

3
Summary by Whatamidoing (WMF)
Paper9oll (talkcontribs)

Is there an option to turn off the autosuggest in edit summary without turning off the browser option? As the current default editor doesn't have autosuggest and I didn't need to tweak my browser option.

In addition for syntax highlighter, templates, magic words and bolded words are not bold hence would like to request it to be bold like in the current editor. If this is new behavior for templates and magic words, I think I can accept it. However, for bolded words, it should function the same as italics words where there is no need to click preview to confirm if it's working because the editor (wikitext mode) would display it as italicized automatically when the sentence/word is applied with italics.

Whatamidoing (WMF) (talkcontribs)

There is no way to turn off the edit summary search. (It searches your most recent 200 edit summaries at that wiki.)

Because of limitations in the original CodeMirror (syntax highlighter) software, they have to choose between not having bold (and anything else that changes the width/size of characters) in the 2017WTE, or not having it be readable in some web browsers (e.g., Firefox). Unless CodeMirror gets a substantial update – which seems doubtful – we won't get anything displayed in bold text.

Paper9oll (talkcontribs)

Okay I would like the option to turn off the edit summary autosuggest if it could be implemented as an option feature that could be turn on/off via the preferences.

Hopefully, CodeMirror get updated for 2017WTE, so bold text works correctly in Firefox.

Thanks you for taking the time to reply. Cheers and have a good weekend.

Reply to "Edit summary and suggestion for Syntax highlighter"

A few suggestions

2
Summary by Whatamidoing (WMF)
Berrely (talkcontribs)

Hi! I really love the 2017 Wikitext editor, especially some of it's features like Citoid and iinteigration the visual editor. After using it, I have a few suggestions.

  • When created a redirect, append ?redirect=no to the end of the URL so you stay on the page.
  • Preview: I know this is unlikely to be implemented, but not that I have to click 4 times to see a preview and go back to editing, it has massively discouraged me from using the preview button. It would be nicer if it was just to the left of the "publish" button or similar.

That's all I can think of for now!

Whatamidoing (WMF) (talkcontribs)

I'm glad that you like it. I find that I'm more likely to use m:Help:Keyboard shortcuts to preview a page. The exact keys depend on the type of computer, but it's Control+ Option+p on a Mac.

Reply to "A few suggestions"
2A01:6500:A046:58AB:A347:A748:1A3C:1C01 (talkcontribs)

One of the editor's container elements has the mw-parser-output class. While that makes a lot of sense when editing on visual mode, applying it to source editing mode may cause leakage of styles which are meant to be applied to Wikitext output, not to source code view.


This may become especially problematic when using syntax highlighting, as styling may ruin the alignment between the invisible textarea element and the visible p elements, making it almost impossible to edit. Example: https://community.fandom.com/f/p/4400000000003199281


I would suggest removing that class when the wikitext mode is active. ~~~~

Whatamidoing (WMF) (talkcontribs)

Wikia's Fandom is a third-party website. You should contact that website's owner about problems you encounter there.

Reply to "Class mw-parser-output"
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"