Talk:2017 wikitext editor/2023

Hi, thanks for your interest in the 2017 wikitext editor. Please post all feedback at 2017 wikitext editor/Feedback, in any language. Thank you!

Is there a way to invoke specific editor

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

---

If I have this editor enabled can I still use 2010 wikicode editor (textarea)? For example let's say I want to open editor for some specific action or gadget.

Or the other way around. Let's say I prefer 2010 wikicode editor for everyday use. But then I want to edit some article in 2017 editor. I actually often do wish that. E.g. to have tools for refs or just for testing. Nux (talk) 15:01, 6 January 2023 (UTC)

OK, found a way to use plain textarea editor. Using action=submit works to always show so called 2010 editor. Nux (talk) 15:37, 6 January 2023 (UTC)

That's the way that I do it. :-) Whatamidoing (WMF) (talk) 04:47, 10 January 2023 (UTC)

The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

Inaccurate plans and wording

The article is outdated and inaccurate, mostly about plans. It seems like the article was never really updated since 2017. Especially in paragraph "Please note that the current phase of deployment is...".

There are serious drawbacks to using VE surface (very specific API to use). Using contenteditable gives some potential to avoid problems with text selection, copy&pasting, undo&redo and such. But also adds a significant overhead as there is no single API that works for all editors for that. I imagine this was the reason this editor didn't ever stick.

Also new features seem to be developed for so called 2010 editor (e.g. syntax highlighting, realtime preview). So the 2017 editor seems to be abandoned. Never even made out of beta to be a standard preference. I think the best option would be to be able to switch to this VE wikicode editing mode. Much like when you switch just one option to get syntax highlighting. Another option would be to integrate features of 2017 editor to syntax highlighting mode of 2010 editor. It would provide best experience for editing sections and at least short articles.

The naming is also very miss leading. I would call this a VE Wikicode Editor or Visual Wikicode Editor. It is a wikicode editor, but it's based on VE components. So called 2010 editor has been updated in many ways and calling it 2010 edit is missleading. I would call the 2010 editor the Standard Wikicode Editor or the Textarea Wikicode Editor. Nux (talk) 16:52, 6 January 2023 (UTC)

@Nux, thanks for tagging the page {{Outdated }}. The project has been undead for six years. In early 2017 the EnWiki community consensus rejected 2017Editor.[1] One or more staff were unwilling to let go of their goal of somehow someday pushing all editors into the VE-platform, so 2017Editor became yet another zombie/vampire project slowly eating time and money.

I've been considering opening another RFC so the community can push the WMF to face reality. Either the WMF intends to forcibly impose 2017Editor against community consensus, or the project needs to be shut down and removed from beta-options. (Actually they also have the option of opening dialog with the community, hoping to change consensus - but I wouldn't expect success.) I see you're primarily from Polish Wikipedia? Feel free to ping me if you (or anyone else) wants to open this or any similar issues over there. In my experience it can take active rejection from EnWiki plus two other big wikis before top management receive the message that mid/lower management are wasting money because they're unwilling to shut down a known-dead pet project. Alsee (talk) 23:36, 6 January 2023 (UTC)

Annoying movement within text box

Tracked in Phabricator
Task T334994

At certain screen resolutions, the text box view itself seems to move left and right internally. To reset it, you need to go all the way to the left. It is especially annoying because this incorrect behaviour is default on the standard text width in new Vector. If this could be fixed, it would go a great way toward usability. Ifly6 (talk) 09:59, 14 March 2023 (UTC)

Are you still having this problem? (I know that one bug was fixed already.) Whatamidoing (WMF) (talk) 23:14, 30 March 2023 (UTC)

I am still having this issue. The issue only occurs when making the width of the window something that isn't a full integer multiple of the monospaced text. In such a case, the internal screen moves to show the remainder by moving to the right. Ifly6 (talk) 01:03, 31 March 2023 (UTC)

I'm still getting this issue; for some reason it seems that the internal screen moves when the cursor is near the end of the line rather than when it actually gets beyond the end of the line. I don't know why that is the case.

Regardless, it is annoying because it screws up the carat display and makes text selection inaccurate. Ifly6 (talk) 17:27, 18 April 2023 (UTC)

I've not been able to reproduce this. Is there any chance that you could make a short screencast and e-mail it to me? I'll send you a quick e-mail message now that you could reply to.

I've started a bug report at phab:T334994 (you're welcome to edit it; just log in to your regular wiki account), but I don't know if Phabricator accepts videos. Whatamidoing (WMF) (talk) 20:21, 18 April 2023 (UTC)

I'm currently at work but I can reproduce the error on my iPad browser too. Uploaded as an unlisted video at https://youtu.be/kUvwP7RsxFs. Ifly6 (talk) 20:40, 18 April 2023 (UTC)

I can also reproduce after commenting out everything in my commons.js file. Ifly6 (talk) 20:45, 18 April 2023 (UTC)

That looks terrible. I'll ping the devs. Whatamidoing (WMF) (talk) 17:09, 21 April 2023 (UTC)

I can't log in to Phabricator and don't receive any emails that it alleges to send. I saw that someone can't reproduce. I have no ability not to reproduce on English Wikipedia; I've disabled every gadget but default, disabled everything in common.js, changed themes (back to Vector 2010 and it still has this issue). I've switched computers from iPad to macOS to Windows. Ifly6 (talk) 03:33, 25 April 2023 (UTC)

It's even worse on Firefox, where it double-displays text like this: https://imgur.com/DqLCI4z. Ifly6 (talk) 03:37, 25 April 2023 (UTC)

Okay, I disabled the beta feature for discussions after comparing my main account's settings with a puppet account's settings; it seems there is some kind of incompatibility with the Discussion tools beta feature? Ifly6 (talk) 03:42, 25 April 2023 (UTC)

Actually I can still reproduce even with Discussion tools disabled. It seems, however, to trigger with much lower sensitivity? Ifly6 (talk) 04:03, 25 April 2023 (UTC)

Okay, Ifly6 here on a clean account for testing; I am unable to reproduce in the editor if syntax highlighting is off but it does reproduce if syntax highlighting is enabled. Transilvanium (talk) 04:21, 25 April 2023 (UTC)

@DLynch (WMF) is one of the devs on the Editing team.

Does turning off syntax highlighting solve the problem in your regular account? Safemode might be an easier way to test some of this, but you sound like a technically capable person, so do you know how to check for errors in your browser's web console? (No problem if you don't – I ask the devs every time they want me to do this. ;-) ) Whatamidoing (WMF) (talk) 19:58, 1 May 2023 (UTC)

Turning off syntax highlighting does solve the issue in my normal account; though given how useful syntax highlighting is, this is not really a solution. I tested with safe mode and am able to reproduce the movement when syntax highlighting is turned on. I opened the developer console and saw no errors. Ifly6 (talk) 00:32, 2 May 2023 (UTC)

Also, as I checked the ticket in Phabricator, thanks for moving it up the chain and identifying (possibly) the relevant library. Ifly6 (talk) 00:34, 2 May 2023 (UTC)

@Ifly6, @MusikAnimal (WMF) wondered whether this problem appeared for you in the 2010 wikitext editor (the most common one in Wikipedias). If it doesn't, he's got an idea about a temporary fix. The (possible) real fix might happen later this year. Whatamidoing (WMF) (talk) 22:37, 20 May 2023 (UTC)

Regular expression replace doesn't work

It seems that find and replace for a regular expression match doesn't work on English Wikipedia. I've tested this largely on Windows 10 Edge. Ifly6 (talk) 17:26, 18 April 2023 (UTC)

Would you please share more information about what exactly you were trying to do? It might be a general problem, but also just a browser-specific problem or a JavaScript limitation. Matěj Suchánek (talk) 08:02, 20 April 2023 (UTC)

I ran a regex, I think {{Code

| inline = 1

| 1 = (?<=\d{3}) (?=BCE?)

}} with replacement value {{Code

| inline = 1| 

}}; replacement simply didn't work. I exported the text to Sublime Text where it ran fine. Ifly6 (talk) 14:02, 20 April 2023 (UTC)

Indeed, that doesn't work for me either. (\d{3}) (BCE?) → $1 $2 does, though. Matěj Suchánek (talk) 16:28, 20 April 2023 (UTC)

This issue still isn't fixed. Running a regular expression

\|url=.+?worldcat.+? (?=\|)

yields the same problem. Ifly6 (talk) 01:54, 14 May 2023 (UTC)

Reported as phab:T336635. Matěj Suchánek (talk) 10:16, 14 May 2023 (UTC)

Text highlighting requests

I have two questions:

• Is it possible to get text highlighting for text that is inside a reference tag?
• Is it possible to fix the bug with images where the text highlighting ends with the first set of ]] instead of where it actually ends? Ifly6 (talk) 17:30, 18 April 2023 (UTC)

These are both questions for CodeMirror. The first is a feature request and the second should be filed as a bug. You can write them up yourself, if you'd like. Whatamidoing (WMF) (talk) 20:22, 9 June 2023 (UTC)