2017 wikitext editor/Feedback/2017/01

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).

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

Edited page removed from Watchlist

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.

---

I've noticed that if you do this type of edit:

1. Open VisualEditor
2. Change to 2017 WikiEditor
3. Save (still not having check box for "Minor edit" and "Add to watchlist")

The page you have just saved is removed from your Watchlist. Mannivu · ✉ 12:54, 1 January 2017 (UTC)

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

Search broken

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.

---

I've noticed that, using Chrome, when I've enabled the 2017 WikiEditor the Search bar doesn't work correctly: I can search, but I don't get any suggestion. This happens only when I can't edit using 2017 WikiEditor. I explain better: in ns0, using Chrome, most of the time I don't get the 2017 WikiEditor when I click "Edito source"; in this case, the search bar doesn't work. But, if I move to another namespace (for example, User talk ns) the search bar works correctly and I can edit with the 2017 WikiEditor. Mannivu · ✉ 13:22, 1 January 2017 (UTC)

Do you mean the search bar outside of VisualEditor? It works fine for me. Do you have any extra gadgets or user scripts? Are there any erorrs in the console (F12)? ESanders (WMF) (talk) 17:47, 2 January 2017 (UTC)

I've installed some gadgets (I don't know if this helps, but I've got also a problem with the gadget "Navigation Popup"), but I have this issue only when using Chrome. Also, I've got this Error in the console:

Error: Bad constructor arguments Error: Bad constructor arguments
    at Uri (eval at <anonymous> (/w/load.php?debug=false&lang=it&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=1u1uxh5:4), <anonymous>:211:546)
    at HTMLAnchorElement.eval (eval at <anonymous> (/w/load.php?debug=false&lang=it&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=1u1uxh5:4), <anonymous>:232:5)
    at Function.each (/w/load.php?debug=false&lang=it&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=1u1uxh5:5)
    at jQuery.fn.init.each (/w/load.php?debug=false&lang=it&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=1u1uxh5:2)
    at HTMLDocument.eval (eval at <anonymous> (/w/load.php?debug=false&lang=it&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=1u1uxh5:4), <anonymous>:231:980)
    at fire (/w/load.php?debug=false&lang=it&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=1u1uxh5:45)
    at Object.add [as done] (/w/load.php?debug=false&lang=it&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=1u1uxh5:45)
    at jQuery.fn.init.jQuery.fn.ready (/w/load.php?debug=false&lang=it&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=1u1uxh5:49)
    at jQuery.fn.init (/w/load.php?debug=false&lang=it&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=1u1uxh5:41)
    at jQuery (/w/load.php?debug=false&lang=it&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=1u1uxh5:1)
logError @ /w/load.php?debug=false&lang=it&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=1u1uxh5:176

Mannivu · ✉ 17:58, 2 January 2017 (UTC)

Does the search work as expected if you disable the beta feature? Whatamidoing (WMF) (talk) 01:55, 21 January 2017 (UTC)

Yes, I've got no problem when I disable the beta feature. Mannivu · ✉ 19:05, 21 January 2017 (UTC)

Can you tell us what wiki you are on, and which gadgets you have enabled (in addition to the default ones). ESanders (WMF) (talk) 11:39, 22 January 2017 (UTC)

I'm on itwiki and I've a lot of gadgets enabled. But after disabling every gadget the issue is gone. So probably is some gagdet having conflicts with something. After a few try, I've noticed that it has probably something to do with die gadget W:it:MediaWiki:Gadget-DeleteSection.js which allows the quick deletion of a section of the page. So probably it has something to do with that. I'll ask in itwiki hel pages and let you know if we found out something. Mannivu · ✉ 13:08, 22 January 2017 (UTC)

I think it might be a case of stuff not loading quickly. I've seen this a few times myself. Whatamidoing (WMF) (talk) 19:04, 23 January 2017 (UTC)

Can reproduce with that gadget enabled, have filed a bug with the cause: T156282. ESanders (WMF) (talk) 17:28, 25 January 2017 (UTC)

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

Weergave infobox

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.

---

Op de Nederlandstalige Wikipedia ben ik op het probleem gestoten dat infoboxen niet (volledig) worden weergegeven. In brontekstweergave blijkt alles correct ingevuld, maar in leesweergave is daar niets van te merken. Pas na handmatig alle gegevens opnieuw via de oude brontekstmodus in te voeren is de infobox zichtbaar. Een tweede iets, dat niet onmiddellijk een probleem is maar wel vervelend is: de knop 'handtekening' zit verborgen onder 'invoegen'. Het zou beter zijn mocht je in één klik je handtekening kunnen zetten. Thomas98 (talk) 21:46, 1 January 2017 (UTC)

Can you link to an example? ESanders (WMF) (talk) 17:41, 2 January 2017 (UTC)

This is an example where I had troubles to place the infobox. With this edit all fields of the infobox were filled in correctly but the infobox was not visible. After I asked help on the helpdesk another user made this edit, but he could'nt explane how he dit it. On the helpdesk some other users had the same troubles. Thomas98 (talk) 17:48, 2 January 2017 (UTC)

So extra spaces may be the problem then? I got the same result in my sandbox (and I needed to switch off the beta feature and try with the old editor to recreate). Elitre (WMF) (talk) 18:21, 5 January 2017 (UTC)

Exactly, that's the problem. Thomas98 (talk) 16:21, 6 January 2017 (UTC)

Subbu will look into this when he can. Elitre (WMF) (talk) 17:00, 6 January 2017 (UTC)

I fetched the wikitext for the two revisions and looked at in vi and then looked at the octal dump. It looks like the unicode char U+00a0 (non-breaking space) are present in the infobox args which is tripping up the regexps in the PHP preprocessor since the string "argname\ua0" is no longer argname but an unrecognized arg. So, effectively, the infobox is treated as an empty infobox. I don't know what is the source of these non-breaking whitespace chars ... if it is the new wikitext editor, something in the editor (the human)'s browser .. some cut-paste, etc. That is not something I can tell.

This is confusing precisely because the non-breaking spcae renders as space in the browser and so it is hard to tell looking at it visually that something is broken. SSastry (WMF) (talk) 17:18, 6 January 2017 (UTC)

So, there is no solution at the moment for the problem? Thomas98 (talk) 23:56, 19 January 2017 (UTC)

Subbu, does the <syntaxhighlight lang='text'> tag display non-breaking spaces? (I'm wondering whether the editor copied the template's form from https://nl.wikipedia.org/wiki/Sjabloon:Infobox_aflevering_Star_Trek ).

There is a somewhat similar problem reported at https://www.mediawiki.org/wiki/Talk%3A2017%20wikitext%20editor/2017#h-do_not_justify_text-2017-01-02T23%3A35%3A00.000Z This one might be due to an (unspecified) gadget. Whatamidoing (WMF) (talk) 16:52, 23 January 2017 (UTC)

I think I have figured this out. @LIVE NIEUWS, did you copy the template from somewhere? When you paste multiple blank spaces, like the ones used to make the equals signs line up:

| parameter1     =
| para2          =

then it converts those spaces into non-breaking spaces. (This is because multiple spaces usually get treated as one space in HTML.)

As a temporary workaround, try using the Insert > Template tool instead.

I thought that there was already a bug report about this, but I can't find it. I've started phab:T156498 instead. Whatamidoing (WMF) (talk) 17:04, 27 January 2017 (UTC)

Thank you for anwering :) ! Yes, I copied the template from the template page (wich I usually do). Thomas98 (talk) 17:38, 27 January 2017 (UTC)

Sorry @Whatamidoing (WMF) .. I was in the process of travelling to India and lost track of this. But, looks like you guys figured out what is going on here. SSastry (WMF) (talk) 04:34, 28 January 2017 (UTC)

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

Suggestion: "Intelligent" interwiki link conversion

Greetings wikitext editors!

I've been using the new editor for a while now, and I really appreciate the way that copying a Wikipedia URL into the editor automatically formats it to be an internal wikilink. It's one of those features that might help newcomers who want to link to another article but don't know how the wikilink system works.

However, when I paste a link from en-wiki onto da-wiki, it's still treated as if it was an internal article on da-wiki. Would it be possible to make an (optional?) feature that detects if the link comes from another wiki and automatically adds the [[:en:]] prefix to the link? This could also apply to interwiki links to other projects (i.e. [[meta:]]).

Would this be possible? InsaneHacker (talk) 08:54, 3 January 2017 (UTC)

As I can remember, I saw phabricator issue on this. IKhitron (talk) 12:42, 3 January 2017 (UTC)

Last time you answered my analogous question with this llink:

https://phabricator.wikimedia.org/T153624 Gżdacz (talk) 19:21, 4 January 2017 (UTC)

It looks like this will be a "can't have both" issue. We can either:

1. turn all URLs (from all wikis known to the inter wiki map) into local wiki links, *or*
2. leave URLs alone.

What's not available for technical reasons (even though we'd all prefer it) is:

• magically turn local URLs into local wiki links (e.g., [[link]]) and 'foreign' URLs into interwiki links (e.g., [[:m:Link]]).

I haven't talked to the team about this, but I believe that they are open to either of the first two options. They're going with option #2 at the moment, but if you'd rather have option #1, then please speak up. Whatamidoing (WMF) (talk) 16:58, 23 January 2017 (UTC)

What about doing both and letting the user choose one in his/her configuration?

I expect that #1 would do better as the default for new users and those editing from IP. Gżdacz (talk) 17:51, 23 January 2017 (UTC)

Individual configurations usually create performance problems, and we'd still have to decide on a default setting (which nearly all users would keep). Whatamidoing (WMF) (talk) 18:56, 23 January 2017 (UTC)

What kind of performance problem might this configuration option create?

#1 seems to be the right choice for default. I guess that the need to link beyond local wiki comes only later, when users advance in skills and start undertaking more complex edits. Gżdacz (talk) 19:12, 23 January 2017 (UTC)

One more comment:

In my opinion #1 is better for newcomers and IPs, #2 is more comfortable for advanced users.

You are asking your question here, where newbies are probably severely underrepresented. Therefore the answers collected here are likely to be biased. Gżdacz (talk) 19:29, 23 January 2017 (UTC)

@InsaneHacker, what's your preference between #1 and #2? Even if it's configurable per account, there must be a default/starting position. Whatamidoing (WMF) (talk) 07:12, 25 January 2017 (UTC)

I think #1 would be best as the standard, and #2 as an optional setting. InsaneHacker (talk) 09:22, 25 January 2017 (UTC)

They did that originally, and we got complaints about it. Perhaps it needs to be smarter about it (translate interlanguage links but not interwiki links, or something like that). Whatamidoing (WMF) (talk) 23:10, 15 February 2017 (UTC)

Ctrl+F do not work

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.

---

Ctrl+F is Browserstandard for Search on page, so the shortcut for find and replace-Funktion do not work as expected. 91.114.82.162 (talk) 12:30, 7 January 2017 (UTC)

VE has build in find and replace which binds to CTRL+F and works fine for me. You can also get the browser's find functionality if you focus outside of the edit area. ESanders (WMF) (talk) 23:43, 10 January 2017 (UTC)

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

Is there a guide, how to add userscripts to the new text 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.

---

as of now I can not use my userscripts with new text editor ⵓ (talk) 12:35, 7 January 2017 (UTC)

There is a guide to writing gadgets for VisualEditor. ESanders (WMF) (talk) 23:42, 10 January 2017 (UTC)

Fantastic, looking forward to a new Syntax highlighter for it. Overall, seems a fantastic improvement of the existing editor. T.Shafee(Evo﹠Evo)^talk 01:45, 12 January 2017 (UTC)

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

HTML code opening instead of wikitext

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.

---

I don't know what is happening but for a couple times today (each time trying to edit a section) first the old text editor opened, and then the 2017 editor loaded opening the (full) HTML code of the page instead of the wikitext. It is quite odd. Going back and clicking edit again sometimes solves the issue. Máté (talk) 12:41, 7 January 2017 (UTC)

Hi, Máté. The bug was fixed and will be deployed at January 19. See phab:T153508 for details. IKhitron (talk) 14:09, 7 January 2017 (UTC)

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

Deleting page while editing

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.

---

I managed to delete everything on a discussion page whilst using the new editor. At first I was refused to see a preview (the preview never showed up) and when I reloaded I was told that there had been an editing conflict. If one takes a look in the history, there isn't any conflict (or is there?). What happened? Anything to do with the new editor or did I just have a bad edit? Orf3us (talk) 10:55, 10 January 2017 (UTC)

Thanks for this note. That's Phab:T154217. They're still trying to figure out what's broken. Whatamidoing (WMF) (talk) 20:21, 19 January 2017 (UTC)

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

Moving Preview Button from "save page" dialogue to a button next to save page

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.

---

Hello,

i'm a bit confused because i have to press the "save changes" button to get the possebility to preview my changes. I think it irritates. It would be nice to have a separate button to get thee preview window opened.

Thanks Pearli (talk) 14:53, 13 January 2017 (UTC)

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

No "wikificator" (викифицировать) button in Russian Wikipedia

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.

---

I often use the functionality of auto-fixing the markup and the text (replacing "" with «„“», -- wit — etc). It is absent in the new editor.

It is used in ru and uk wiki, and few others—here is Russian description page [1] .

I would appreciate adding that button. This is functionality that really helps, I press it at least once per editing. The new editor is wonderful, but I must revert to the old one until this functionality is present...

Thank you. EUvin (talk) 10:56, 14 January 2017 (UTC)

Здравствуйте, EUvin. К сожалению, выполнить вашу просьбу теоретически невозможно. Викификатор не является частью программного обеспечения Медия-вики, а написан русскоговорящими программистами специально для русскоязычного радела Википедии. Для подключения к ядру программы он использует интерфейс гаджетов старого редактора. Новый редактор не имеет никакого отношения к старому — он является расширением Визуального редактора, у которого абсолютно другой интерфейс гаджетов, более того, его строение чрезвычайно затрудняет возможность создать там что-либо ценное. Поэтому единственный шанс выполнить Ваше пожелание, это написать новый викификатор, с самого начала, по-видимому намного менее мощный, под интерфейс Визуального редактора. Это работа намного более сложная чем создание оригинального Викификатора в свое время, поэтому вы можете попробовать найти заинтересованных программистов на Техническом Форуме вашей Википедии, готовых затратить на это много месяцев, но я очень сомневаюсь, что из этого выйдет что-нибудь путное. IKhitron (talk) 13:56, 14 January 2017 (UTC)

Печально. Думаю, включение нового функционала в рувики будут так или иначе обсуждать затрагивая тему Викификатора. Я не настолько глубоко вовлечен в проект с технической стороны. Спасибо что прояснили вопрос. EUvin (talk) 01:23, 15 January 2017 (UTC)

Не за что. А кстати, EUvin, существует техническая возможность постоянной работы с новым редактором, и в случае необходимости включения старого, прямо из нового или из состояния чтения, например. Всё что нужно, это запустить страницу с параметром "action=edit" вместо "veaction=editsource" в новом редакторе или "veaction=edit" в визуальном. Создать соответствующую кнопку, чтоб это было автоматически, а не каждый раз вручную - минутное дело на джаваскрипте. По моему, это может помочь и Вам лично, и вашему обсуждению. IKhitron (talk) 01:41, 15 January 2017 (UTC)

Спасибо, но думаю что надо найти/начать обсуждение этого где-то в рувики, т.к. я сейчас не в силах освоить джаваскрипт и дописать какой-то еще плагин, я шаблоны на вики-разметке с трудом пилю) Инициировал тему для этого на странице обсуждения Викификатора в рувики. Посмотрим, может там есть умы необходимые для решения проблемы такого уровня сложности. EUvin (talk) 11:35, 15 January 2017 (UTC)

Summary in English: it seems that new editor cannot support the «wikifier» tool (plug-in), which is very important for Russian Wikipedia community. It can be a problem for Russian Wikipedia switching to the new editor. EUvin (talk) 12:01, 15 January 2017 (UTC)

I answered there. IKhitron (talk) 12:32, 15 January 2017 (UTC)

Hi there. Has anyone tried to contact the author of such a tool to figure out which help they need to make it compatible with the 2017 wikitext editor? Elitre (WMF) (talk) 11:25, 19 January 2017 (UTC)

Hello, the tool seem to be originating in Russian Wikipedia, so I started new theme on the tool's discussion page [2]. Noone answered yet... EUvin (talk) 12:11, 19 January 2017 (UTC)

OK, this is the way to go :) Elitre (WMF) (talk) 12:16, 19 January 2017 (UTC)

I filed this as Phab:T156025 because I didn't want to lose these links, and because we might want to make a list of critical gadgets.

How does this gadget compare to using ULS's built-in system? Whatamidoing (WMF) (talk) 17:11, 23 January 2017 (UTC)

Hello, not sure I understand your question... This gadget fixes markup to match Russian typography rules mostly, and also make the markup "prettier" (removing few not needed lines here and there, making spaces like: ==Title== → == Titile == etc). Editor just presses a button and voila text looks much better without any effort. EUvin (talk) 09:53, 24 January 2017 (UTC)

I thought the gadget was similar to a "special character" inserter. Some languages have gadgets because some characters are difficult to type. The built-in ULS system is often a good alternative for them. But it doesn't do other changes, such as ==Title== → == Title ==.

(@Bgwhite and @Magioladitis, have either of you ever seen a 'wikificator' gadget that does whitespace changes? I wonder if it might be popular and/or useful for correcting CHECKWIKI-type errors.) Whatamidoing (WMF) (talk) 07:07, 25 January 2017 (UTC)

meta:User:TMg/autoFormatter is a really good gadget. The author, TMg, is really smart, helpful and wonderful to work with. autoFormatter runs on enwiki and dewiki, but it can be localized. The button is installed next to the B I (bold italic) on the editing toolbar.

en:Wikipedia:AutoEd is another option. It currently runs on enwiki, arwiki and fawiki. The "button" is installed on the top menu tabs under the "more" tab.

Both fix CheckWiki errors, but autoFormatter is usually more upto date. Bgwhite (talk) 07:53, 25 January 2017 (UTC)

Note: by "Russian typography rules" I mean changes like these, that Wikifikator also does:

Next is dash - and here is "Some "company" name"

transforms to:

Next is dash — and here is «Some „company“ name»

There is more, but I am not developer of this tool and I only noticed abovementioned changes that the tool does. EUvin (talk) 10:23, 25 January 2017 (UTC)

EUvin, autoFormatter already does what you mentioned. On enwiki, it does quotes and dashes per English conventions. On dewiki, it does quote and dashes per German conventions. It would be a matter of getting autoFormatter localized for Russian. Bgwhite (talk) 11:02, 25 January 2017 (UTC)

I added support for the double quotes the Russian Wikipedia uses to the beta version of my script. TMg 16:39, 25 January 2017 (UTC)

Per James on Phab: Is there anyone from the Russian Wikipedia community intending to take this on? Do they need any support/advice/assistance? Thanks. Elitre (WMF) (talk) 14:29, 27 March 2017 (UTC)

I left note about this on Ru-Wiki's forum. Thank you. EUvin (talk) 11:04, 28 March 2017 (UTC)

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

MediaWiki:Newarticletext

On cswiki we deal with a little problem. For OWE we have got a long intro when creating a non-existing page (take a look), but in NWE/VE that long text is transcluded into this small notice box (take a look).

Shouldn't this be in some form of editintro as it is in OWE (task on phabricator)? Is there a way how to make different MediaWiki:Newarticletext for OWE and VE/NWE? Is there a way how to hide the whole notice (e.g. by user script) Dvorapa (talk) 16:30, 14 January 2017 (UTC)

If you want to hide a notice, then you get the name of the MediaWiki message, and add a line to your CSS file, as was done here: https://www.mediawiki.org/wiki/Help%20talk%3ACirrusSearch/2017#h-Special_page_%3A_disable_text_and_tables/templates-2017-01-17T19%3A11%3A00.000Z

https://cs.wikipedia.org/w/index.php?title=New_article&action=edit&uselang=qqx will show you the name of the messages on the page. I think you're looking for w:cs:MediaWiki:Newarticletext. Whatamidoing (WMF) (talk) 17:23, 23 January 2017 (UTC)

I'd say the bug here is that MediaWiki allows an absurd amount of text in its interface messages (presumably up to 2MB), which is insane. The bug fix would be to limit it to a discrete amount of characters, and also outright ban wikitext / html in many of these messages because in some cases users have changed this from being a simple message to a huge wall of text.

A good current example is the meta:Special:Recentchanges, the interface message is so big that it uses up more than half of a screen, and together with the form fills a whole screen on a 1200 x 800 resolution. No "recent changes" can even be seen on a recent change page. Even with larger screens it is a lot of unnecessary information that certainly nobody reads.

Many editors probably don't know this, but if misused the interface message can considerably slow down page load if certain expensive parser functions are used, e.g. if someone would be mad enough to use Extension:Dynamic page list or potentially the category tree on one of these. 197.218.83.179 (talk) 17:32, 23 January 2017 (UTC)

Meta seems to have M:Template:Recentchanges/text added to RecentChanges via M:MediaWiki:Recentchangestext (putting it in a template makes it translatable on wiki via Extension:Translate rather than through the direct method of creating MediaWiki:Recentchangestext/xx for each language). I think you'd have to ask the admins there why they decided that this was useful for that wiki. Whatamidoing (WMF) (talk) 19:02, 23 January 2017 (UTC)

> I think you'd have to ask the admins there why they decided that this was useful for that wiki.

No need to ask, it is simply ignorance.

In fact, it not only proves the point. While most people may translate the pages someone may easily add a very slow parser function, or if the translate extension allows any markup, someone could easily add the image of a naked person all over the screen the exact way that was done in the hillary clinton article.

Interface messages are deliberately protected for a reason. 197.218.83.179 (talk) 19:39, 23 January 2017 (UTC)

Editing a redirection

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.

---

I have recently changed my username. I therefor had to edit some redirects on different Wikis. I saw that, on some Wikis, editing a redirection with the modern wikitext editor will edit the page which is redirected to and the redirect.

Other than that the new editor is more aesthetic and more ergonomic then the "normal" wikitext editor. Niridya (talk) 00:12, 15 January 2017 (UTC)

I use Chrome 55, Windows 10 64bit and Vector skin :) Niridya (talk) 00:13, 15 January 2017 (UTC)

Hi @Niridya, I'd appreciate if you pointed to the specific example here. TY! Elitre (WMF) (talk) 12:23, 19 January 2017 (UTC)

Try these links:

https://www.mediawiki.org/w/index.php?title=ULS&redirect=no&veaction=editsource opens the redirect. https://www.mediawiki.org/w/index.php?title=ULS&veaction=editsource opens the target page.

I've started a task at phab:T156042. Whatamidoing (WMF) (talk) 18:18, 23 January 2017 (UTC)

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

Not possible to check categories

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.

---

When editing a page it's not possible to check if categories are correct or not. The preview shows the article, but not the categories. So it's very well possible to end up with red category links that need to be edited again to correct them. Mbch331 (talk) 12:10, 15 January 2017 (UTC)

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

"something strange"

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.

---

Clashes various editing and reading as doing odd source code editing paragraph

examples:

https://he.wikipedia.org/w/index.php?title=%D7%A1%D7%99%D7%99%D7%A0%D7%98_%D7%90%D7%95%D7%92%D7%95%D7%A1%D7%98%D7%99%D7%9F&diff=19948305&oldid=19948300

https://he.wikipedia.org/w/index.php?title=%D7%A1%D7%99%D7%99%D7%A0%D7%98_%D7%90%D7%95%D7%92%D7%95%D7%A1%D7%98%D7%99%D7%9F&diff=19953388&oldid=19953351

thanks for answers BDaniel (talk) 13:01, 15 January 2017 (UTC)

if you know hebrew (I used google translate from this language):

"התנגשויות עריכה שונות ומוזרות קוראות כשעושים עריכת קוד מקור בפסקה" BDaniel (talk) 13:03, 15 January 2017 (UTC)

@Elitre (WMF), in both cases it looks like the user edited a section, and only that section was saved and the rest of the article was discarded. Looks like a bug. Amir E. Aharoni {{🌎🌍🌏}} 14:53, 19 January 2017 (UTC)

@BDaniel, @Amire80, any chance we can get steps/ideas about how to reproduce the problem? More details about user's configuration are also welcome! Elitre (WMF) (talk) 17:06, 19 January 2017 (UTC)

That's phab:T154217. This has happened to several editors during edit conflicts. They have not found the cause yet. All information is wanted. Whatamidoing (WMF) (talk) 20:25, 19 January 2017 (UTC)

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

Preview

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.

---

The preview is much to effortful to reach – since it is a essential often used feature it should be reachable within one click. MichaelSchoenitzer (talk) 00:40, 17 January 2017 (UTC)

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

Templates

Tracked in Phabricator
Task T156507

I discovered two issues with inserting template:

1) Previewing an edit which inserts a template (by copy pasting in the template code) fails to pick up any of the parameter values (i.e. I get shown a bunch of triple-{)

2) Doing a roundtrip via visual editor kills every single line-break and extra whitespace in the original text. But magically this allows the preview to pick up on the parameters André Costa (WMSE) (talk) 11:06, 17 January 2017 (UTC)

Hi, which template were you testing? Thank you. Elitre (WMF) (talk) 11:12, 19 January 2017 (UTC)

IIRC it was Wmse:Template:Resemall (on wmse chapter wiki) André Costa (WMSE) (talk) 16:22, 19 January 2017 (UTC)

https://phabricator.wikimedia.org/F5334475 is what the template looks like for me when I copy and paste the basic syntax as provided as https://se.wikimedia.org/wiki/Mall:Resemall . Elitre (WMF) (talk) 10:36, 23 January 2017 (UTC)

I created a video showing both the issue with failing parameters, the whitespace mangling when going to VE and then the recovery of the parameters when going back to NWT.

The text which I pasted in was copied from "classic" wikitext. If copying the pre-tagged example from the template documentation NWT does not handle the linebreaks correctly BUT can detect the parameters.

Phabricator didn't seem fond of my ogv video so I uploaded it to Commons instead.

Might be worth breaking this out to a Phabricator task but I was unsure under which project this lives. André Costa (WMSE) (talk) 08:44, 27 January 2017 (UTC)

Your OGV file is 8MB so you're running into https://phabricator.wikimedia.org/T151544 AKlapper (WMF) (talk) 17:27, 27 January 2017 (UTC)

For completness: Running Firefox 50.1.0 on Ubuntu 16.04 André Costa (WMSE) (talk) 08:47, 27 January 2017 (UTC)

I wonder if this is related to what is described at https://www.mediawiki.org/w/index.php?title=2017%20wikitext%20editor/Feedback/2017/01#h-Weergave_infobox-2017-01-01T21%3A46%3A00.000Z . I'll make sure someone looks into this next week, with or without a task! Elitre (WMF) (talk) 10:34, 27 January 2017 (UTC)

Looks Parsoid related. Can we file a bug and tag them? ESanders (WMF) (talk) 17:08, 27 January 2017 (UTC)

https://phabricator.wikimedia.org/T156507 for you all. Elitre (WMF) (talk) 17:47, 27 January 2017 (UTC)

ToC isn't available in preview

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.

---

The preview of the "old" source Editor provided a preview of the site how i would see it if i press the "save changes" button. The New Wikitext Editor is showing me a verison like the VE, so the table of Contents is missing and Images that normally float right under an Information box will be placed on the left side next to it. Thats not how i would like to use a preview. Please fix it. Thanks and best, Pearli Pearli (talk) 08:52, 18 January 2017 (UTC)

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

A Preview panel that doesn't obscure the wikitext edit box (Was: No feature parity)

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.

---

I've just learned about the existence of the 2017 wikitext editor from the WikiProject RfC, and in the first 10 seconds of using it, I'm already missing the single feature I use more often in the classic wikitext editor: showing the page Preview and Changes alongside the text box with the Wikitext.

I've always missed in the Visual Editor that feature, and hated the fact that the "See changes" panel hides the final page below it; but, being visual, showing the Preview wasn't really needed. Not so with the Wikitext editor: here, hiding the page you were editing in order to see the final result is unacceptable.

Please review the workflow of the new editor so that it makes sense for the new use case you're introducing. It's merely a layout change (showing the preview panel above or below the edit page instead of floating and overlapping it), so I hope it shouldn't be exceedingly painful to program. Diego Moya (talk) 15:45, 18 January 2017 (UTC)

@Elitre (WMF) summary said: "I believe https://phabricator.wikimedia.org/T153306 calls for this."

Not really, no. T153306 is about placing the button to access Preview at a more prominent place, and my request is about the having the resulting Preview panel not obscuring the original wikicode.

The request at that request is also nice to have, and both provide improvements to the Preview flow, but they are different changes. I'll try to add my request as a comment at that phabricator page though. Diego Moya (talk) 12:59, 19 January 2017 (UTC)

Finally I've opened a new Phabricator item:

https://phabricator.wikimedia.org/T155732 Diego Moya (talk) 13:17, 19 January 2017 (UTC)

Oh, thanks so much then. Elitre (WMF) (talk) 17:04, 19 January 2017 (UTC)

Thanks for filing that, Diego. I don't remember anyone else asking for that particular ability before, and it's good to have all the ideas in Phabricator. Whatamidoing (WMF) (talk) 19:42, 19 January 2017 (UTC)

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

Find and Replace

Tracked in Phabricator
Task T156196

My favorite function of wikEd is the "find and replace"-tool.

feature	wikED	new Editor
Regexp	implemented	implemented
find and replace field	always visible (switch on/off via localstorage for all tabs)	not visible, need Ctrl+F for each open tab
remember old searchstrings and replacementstrings	via local storage, last used string is default for all following tabs	no systematic storage, simple replacement are partly stored via browser autofill?
replacement only in marked text	support	not supported

features I really need/want

• turn on/off visibility of find and replace from for all following tabs (i.e. by usage of local storage)
• remembering search and replace strings (internal as "s/find/replace/flags"), use local storage or indexeddb
• last used strings are default for next tab/article
• if some text is selected, replace only in selected text
• enable "secure" replacements. look at de:user:TMg/autoFormatter.js ( backup/restore nowikis/filenames-functions)
• Diff-function (I use wikEd-Diff and and de:user:TMg/autoFormatter/autoDiff.js as hook for userscripts like de:User:Boshomi/ARreplace.js, autoFromatter, Boshomi/externalURLform.js (shows diff direct after replacement)

Use case

1. Find pages with cirrus search
2. open 50 tabs of found pages in edit mode (I use API to generated worklist like de:Benutzer:Boshomi/worklist1, but a "edit-link" like special:whatlinkshere, would do the same)
3. perform regexp-replace in all tabs
4. watch the diffs
5. save page if the diff looks good.

do this as fast as possible, avoid mistakes. (I should be possible within 200 seconds or less then 4 seconds per tab, without additional userscripts. If you fail improve the features!) ⵓ (talk) 23:23, 18 January 2017 (UTC)

AWB IKhitron (talk) 23:28, 18 January 2017 (UTC)

no, AWB is no solution. I do not have any .NET on my Linux-Workstation, and I don't like to use external software.

I do edits like de:special:Diff/161935840 only with Browser, and I do it fast. ⵓ (talk) 13:38, 24 January 2017 (UTC)

This is in fact work for an automated tool or a bot, not humans.

There are tools that fit this purpose:

https://en.wikipedia.org/wiki/Wikipedia:WPCleaner - opensource

https://en.wikipedia.org/wiki/Wikipedia:AutoWikiBrowser#See_also - "internal" software.

Doing such edits quickly is a problem in and of itself because reverting them becomes complicated if there are problems, and if someone else edits after it. It seems like a good reason to add better throttling to mediawiki, as 50 open tabs is by no definition of the word normal editing, and is exactly why the bot flag was invented.

Most other suggestions relate either to mediawiki itself, or can be incorporated using [[[gadgets]], as they aren't needed for the wikitext editor. 197.218.90.213 (talk) 14:29, 24 January 2017 (UTC)

I've filed T156196 for find in selection, but I'm hesitant to consider features designed for bot-like edits, as that should not be our focus. ESanders (WMF) (talk) 22:14, 24 January 2017 (UTC)

Neuer Wikitext Editor wird nicht geöffnet, wenn zwei Bearbeitungen hintereinander getätigt werden

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.

---

Hallo,

sobald eine Bearbeitung im NWE gespeichert wird, gelangt man wieder zur Seitenansicht. Sobald auf den Button "Quelltext bearbeiten" geklickt wird (ohne die Seite neu zu laden), gelangt man wider zum alten Wikitext Editor. Dies tritt lediglich auf Diskussionsseiten auf, verwirrt aber trotzdem.

Grüße Pearli (talk) 16:12, 19 January 2017 (UTC)

Danke. I added it to https://phabricator.wikimedia.org/T153561. I hope @Jdforrester (WMF) gets to triage it soon. Elitre (WMF) (talk) 17:01, 19 January 2017 (UTC)

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

Editor reload after switching to another tab in your browser

Tracked in Phabricator
Task T156378

If I switch to another tab on my browser (for looking more information about a subject.) and after a couple of minutes, I return to the editor, the editor reload the page. So, I lost all my edits that I did. That's not handy. I'll be forced to stay on the same tab and can't switch to another tab. Otherwise, I lost al my edits. It happens every time, there are no exceptions. Can you fix it? - (ps; I'm using Google Chome) A second thing is the signature button, it is used by a lot of users but is now hidden and not easily retrievable. I recommend strongly to change this. Thomas98 (talk) 23:54, 19 January 2017 (UTC)

The point about the signature is a known one. For the rest, I'll take a look tomorrow, but automatic reload of the page is not a feature I've heard of. Elitre (WMF) (talk) 18:52, 23 January 2017 (UTC)

I have. It can happen if there is not enough RAM, at least on my tablet. IKhitron (talk) 22:16, 23 January 2017 (UTC)

We know about this on mobile devices, but I haven't heard it happening on desktop. Auto save is T57370, VE getting paged out of memory on mobile is T70017. ESanders (WMF) (talk) 17:18, 25 January 2017 (UTC)

It's on my desktop computer. Thomas98 (talk) 15:53, 26 January 2017 (UTC)

Copy/paste produces gibberish

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.

---

I'm trying to paste a template in the 2017 wikitext editor (following the instructions provided by the {{Non-free reduce }} template).

When I copy and paste the template code, {{subst:orfurrev}}, it is transformed into the following nonsensical code:

<nowiki>{{</nowiki>[[Wikipedia:Substitution|subst]]:[[Template:Orfurrev|orfurrev]]<nowiki>}}</nowiki>

Edit: I've noted that this only happens when I copy the text from the HTML page, not when I copy it from a plain text editor, so this is likely related to the text formatting.

The primary advantage of wikicode is that it is plain text. The wikitext editor should make exactly zero magic transformations, treating everything copied or pasted as a raw Unicode string without formatting. Any such magic should be handled as optional suggestions and provided as an opt-in; otherwise the use case for an enhanced wikitext editor, which gets confused by trivial text paste operations, is doomed to fail.

Oh, and while in Beta (and possibly after that), there should be an easy way to access the classic Wikitext editor. Now in order to edit the page I was working on, I'll have to disable the 2017 editor in the Preferences/Beta options, and I'm not sure I'll re-enable it again. In fact I expected the "edit source" link to me to the classic editor, and that the 2017 editor would be accessible only through the [[ ]] button in the Visual Editor. Diego Moya (talk) 10:38, 20 January 2017 (UTC)

Bug filed: https://phabricator.wikimedia.org/T155821 Diego Moya (talk) 10:53, 20 January 2017 (UTC)

Thanks, Diego. Elitre (WMF) (talk) 18:55, 23 January 2017 (UTC)

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

More feedback from Josve05a

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 Josve05a (talk) 20:04, 20 January 2017 (UTC)

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? Elitre (WMF) (talk) 18:47, 23 January 2017 (UTC)

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. Josve05a (talk) 20:43, 23 January 2017 (UTC)

For 1, you can always use CTRL+SHIFT+V to force paste plain text though. Conversation continues at https://phabricator.wikimedia.org/T153315. Elitre (WMF) (talk) 10:47, 24 January 2017 (UTC)

(Which FWIW was resolved.) Elitre (WMF) (talk) 17:23, 12 July 2017 (UTC)

Update: Expect some improvements when pasting things from the <syntaxhighlight lang='text'> 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. Whatamidoing (WMF) (talk) 23:03, 15 February 2017 (UTC)

Re #4, see https://www.youtube.com/watch?v=YRprzyIbydU Josve05a (talk) 20:58, 23 January 2017 (UTC)

#4 is reported here: https://phabricator.wikimedia.org/T154329 Stryn (talk) 18:51, 23 January 2017 (UTC)

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). Whatamidoing (WMF) (talk) 19:11, 23 January 2017 (UTC)

I'm using chrome on a chromebook with chromeOS. Josve05a (talk) 20:37, 23 January 2017 (UTC)

On #3, it's working for me in Firefox and Safari. Whatamidoing (WMF) (talk) 19:12, 23 January 2017 (UTC)

@Josve05a, Can you try in incognito, from another browser, etc.? Elitre (WMF) (talk) 10:51, 24 January 2017 (UTC)

Error

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.

---

[WIdFfgpAIDwAAF4WZgAAAADV] Exception caught: GlobalVarConfig::get: undefined option: 'InterwikiSortingAlwaysSort' MichaelSchoenitzer (talk) 12:18, 24 January 2017 (UTC)

This is not related to this software though, if I'm reading https://phabricator.wikimedia.org/T156123 correctly. Elitre (WMF) (talk) 13:21, 24 January 2017 (UTC)

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

On the new wikitext

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.

---

What I don't like is the fact that the toolbar below the text editor is now missing. I usually switch back and forth for things like editing templates. Really annoying. Piranha249 (talk) 23:44, 24 January 2017 (UTC)

What do you mean by "the toolbar below the text editor"? (Do you mean the special character inserter?) Whatamidoing (WMF) (talk) 07:01, 25 January 2017 (UTC)

Yes, the special character inserter, which I use to add things like redirect and <--- ---->, amongst others. Piranha249 (talk) 23:04, 25 January 2017 (UTC)

There is a special character inserter in the toolbar. Click the "Ω" button to see it. At the top of the list is an "Often used" option, which can be customized locally (per wiki, not per user).

Some of the other things that you want are in the toolbar. For example, hidden HTML comments can be added from the menu: Insert > More > Comment.

For redirects, I think you'll have to switch to visual mode first. It's in the "three bars" menu (near the Save button), and you need the "Page settings" item. Whatamidoing (WMF) (talk) 07:03, 26 January 2017 (UTC)

Thanks for the response, I'll try and find it... Piranha249 (talk) 21:48, 26 January 2017 (UTC)

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

show/hide

In the preview does not work "show/hide". Try to edit and preview the template ru:Шаблон:Хранилище_данных. Sunpriat 19:32, 27 January 2017 (UTC)

Just helping with instructions to reproduce here:

• Go to ru:OLAP.
• Edit with NWE.
• Save -> Preview
• Scroll down to the infoboxes.

Observed: Clicking the links to show/hide ([скрыть]) doesn't do anything. Amir E. Aharoni {{🌎🌍🌏}} 10:26, 6 February 2017 (UTC)

This could be a local problem though, because I can't reproduce on en.wp or it.wp? Elitre (WMF) (talk) 10:36, 6 February 2017 (UTC)

this may be local Common.js https://ru.wikipedia.org/wiki/%D0%92%D0%B8%D0%BA%D0%B8%D0%BF%D0%B5%D0%B4%D0%B8%D1%8F:%D0%A2%D0%B5%D1%85%D0%BD%D0%B8%D1%87%D0%B5%D1%81%D0%BA%D0%B8%D0%B5_%D0%B7%D0%B0%D0%BF%D1%80%D0%BE%D1%81%D1%8B#Navbox_.D0.B2_.D0.BD.D0.BE.D0.B2.D0.BE.D0.BC_.D1.80.D0.B5.D0.B4.D0.B0.D0.BA.D1.82.D0.BE.D1.80.D0.B5 Sunpriat 07:57, 13 February 2017 (UTC)

copy 2017/paste 2017 problem

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.

---

1. open for editing https://ru.wikipedia.org/w/index.php?title=%D0%A8%D0%B0%D0%B1%D0%BB%D0%BE%D0%BD:%D0%A1%D0%B8%D0%B3%D0%BD%D0%B0%D0%BB%D1%8B&oldid=80290588 - we see table
2. open for editing https://ru.wikipedia.org/wiki/%D0%A8%D0%B0%D0%B1%D0%BB%D0%BE%D0%BD:%D0%A1%D0%B8%D0%BC%D0%BC%D0%B5%D1%82%D1%80%D0%B8%D1%87%D0%BD%D1%8B%D0%B5_%D0%BA%D1%80%D0%B8%D0%BF%D1%82%D0%BE%D1%81%D0%B8%D1%81%D1%82%D0%B5%D0%BC%D1%8B?veaction=editsource - copy the first five lines
3. insert them in the beginning of 1
4. try to remove the last line of the inserted (say via del and del again) (or other removal of lines)
5. the first line of the template 1 it turns on top, like a flow around the inserted text 2 Sunpriat 20:39, 27 January 2017 (UTC)

Hi,

I'm not sure that I understand the instructions.

2: When you say "copy the first five lines", do you mean these? -

{{Навигационная таблица
| имя = Симметричные криптосистемы
| state = <includeonly>{{{state|autocollapse}}}</includeonly>
| заголовок = [[Симметричные криптосистемы|Симметричные криптосистемы]]
| стиль_четных = background:#f0f0f0

3: So it will be

{{Навигационная таблица
| имя = Симметричные криптосистемы
| state = <includeonly>{{{state|autocollapse}}}</includeonly>
| заголовок = [[Симметричные криптосистемы|Симметричные криптосистемы]]
| стиль_четных = background:#f0f0f0
{{Навигационная таблица
| имя = Сигналы
| state = <includeonly>{{{state|autocollapse}}}</includeonly>
| заголовок = [[Сигналы (UNIX)|Сигналы]] [[POSIX]]
| стиль_четных = background:#f0f0f0
| listclass = hlist

?

Or instead of the existing lines?

And I couldn't really understand number 4 at all. What do you mean by "say via del and del again"? Can you please explain?

(И можно ответить по-русски :) ) Amir E. Aharoni {{🌎🌍🌏}} 11:03, 6 February 2017 (UTC)

@Amire80 Я пытаюсь переоформить шаблоны на hlist, например https://ru.wikipedia.org/w/index.php?title=%D0%A8%D0%B0%D0%B1%D0%BB%D0%BE%D0%BD:SQL&diff=prev&oldid=83499012

Для этого приходится копировать и вставлять. Чем больше вставленный кусок, тем лучше видно.

На том же https://ru.wikipedia.org/w/index.php?title=%D0%A8%D0%B0%D0%B1%D0%BB%D0%BE%D0%BD:SQL&oldid=80226556&veaction=editsource

Вариант 1) скопируем весь шаблон, вставим в текстовый редактор (libre writer или ms office), скопируем из текстового редактора, удалим текст в вики-редакторе, вставим в вики-редактор... a) нажмём сохранить/внесённые изменения и видим что текст как-бы вообще не вставился б) вставленный текст можно удалять клавишей back, но нельзя добавить новую строку, внутри не сработает enter. enter сработает вверху (до вставленного) и внизу (после вставленного), при чем внизу после entera новая строка добавится сверху, как бы обтекая вставленное.

вариант 2) откроем шаблон SQL https://ru.wikipedia.org/w/index.php?title=%D0%A8%D0%B0%D0%B1%D0%BB%D0%BE%D0%BD:SQL&oldid=80226556&veaction=editsource и шаблон SPARC https://ru.wikipedia.org/wiki/%D0%A8%D0%B0%D0%B1%D0%BB%D0%BE%D0%BD:SPARC?veaction=editsource

из шаблона SPARC

| state = <includeonly>{{{state|autocollapse}}}</includeonly>
| класс_списков = hlist

в шаблоне SQL нажмем два раза enter вставив две пустых строки после стиль_четных, получится 3 пустых строки, вставим в среднюю вторую строку скопированный кусок, например чтобы получилось так

{{Навигационная таблица
|имя = SQL
|заголовок = [[SQL]]
|стиль_четных = background:#f0f0f0
| state = <includeonly>{{{state|autocollapse}}}</includeonly>
| класс_списков = hlist
|заголовок1 = Версии
|список1 =

и видим тот же самое - в части state/класс_списков можно удалять клавишей back, но нельзя добавить новую строку

добавим несколько букв

{{Навигационная таблица
|стиль_четных = background:#f0f0f0
| state = <includeonly>{{{state|autocollapse}}}</includeonly>
| класс_списков = hlistaaa
bbb
|заголовок1 = Версии

поставим курсор после aaa и нажмём клавишу del - должен бы удалиться перевод на новую строку и получиться aaabbb, но вместо этого bbb оказывается сверху, то есть как бы обтекая вставленный кусок

{{Навигационная таблица
|стиль_четных = background:#f0f0f0
bbb
| state = <includeonly>{{{state|autocollapse}}}</includeonly>
| класс_списков = hlistaaa
|заголовок1 = Версии

Sunpriat 12:09, 6 February 2017 (UTC)

Сейчас попробую, но прежде всего: зачем копировать в libre writer или ms office? Amir E. Aharoni {{🌎🌍🌏}} 12:16, 6 February 2017 (UTC)

В ms office удобно для hlist заменить всякие шаблоны " • " на обычные списки "^p* " (^p - перевод строки). Попробуйте вставить в notepad блокнот ииз него скопировать в новый редактор, кликнуть куда-нибудь в текст и у вставленного совсем теряются все переводы строк, склеиваясь в одну строку. Sunpriat 12:21, 6 February 2017 (UTC)

Не понимаю. Как ни пытаюсь, у меня всё работает как надо :/

Какие у вас ОС и браузер? Amir E. Aharoni {{🌎🌍🌏}} 12:23, 6 February 2017 (UTC)

icecat 38.8.0 в win10 (все расширения отключал). Попробовал в firefox 53.0a2 - тут действительно нормально вставляется. Sunpriat 12:36, 6 February 2017 (UTC)

So it is quite likely that the old browser is at fault here. Elitre (WMF) (talk) 14:03, 6 February 2017 (UTC)

Нужно где-то прямо написать "в неактуальных версиях браузеров часть функционала может не работать". Иначе странно, что разработчики в одном месте пытаются сделать чтобы всё работало вообще без js, в другом - важный функционал редактирования не работает в версии браузера, которой всего 2 года. Sunpriat 13:14, 7 February 2017 (UTC)

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

Copy/paste problem on huWiki

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.

---

I know that the problem is known, but the copy/paste problem has appeared on huWiki too.

However, there is an another problem too: when I copy and paste a template, the template goes to pieces (see the picture). But if I use a word processor (e.g. Word) I can paste the template but then the template doesn't work. An example: the template is filled out but the datas don't appear.

Best regards, Bencemac (talk) 13:28, 29 January 2017 (UTC)

This is probably https://phabricator.wikimedia.org/T156498. Elitre (WMF) (talk) 09:39, 31 January 2017 (UTC)

@Bencemac, is the problem gone? The task's been resolved. Elitre (WMF) (talk) 15:21, 8 February 2017 (UTC)

Almost. The templates work now rightly (the dates appear after I fill them) but after I paste the template there are “↵” pictograms at the end of the template (see the picture). Bencemac (talk) 15:18, 10 February 2017 (UTC)

I believe that could be https://phabricator.wikimedia.org/T157491 which will land on Wikipedias later this week. Elitre (WMF) (talk) 11:23, 15 February 2017 (UTC)

Thank you! I think now you could close the topic. Bencemac (talk) 14:33, 15 February 2017 (UTC)

I found an another problem while I administrated the good article nominations. I copied a text with <nowiki> wikicode tag from the “how to administrate the nominations?” page, the text got “code” wikicode tags (see the picture, left side). If I use the old editor the text appears well (right side of the picture). Could you help me? Bencemac (talk) 16:26, 10 February 2017 (UTC)

I believe this is https://phabricator.wikimedia.org/T153315 . Elitre (WMF) (talk) 11:16, 13 February 2017 (UTC)

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

Wikitext Conversion

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.

---

When I insert Wikitext, it converts in my wikitext. Sorry for my poor English. Ferdi2005 18:10, 29 January 2017 (UTC)

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

Should I have posted it here?

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.

---

Please look in this thread, perhaps it should have gone here. Grüße vom Sänger ♫^(Reden) 08:10, 31 January 2017 (UTC)

P.S.: The incident happened with a current FF under Mint. Grüße vom Sänger ♫^(Reden) 08:10, 31 January 2017 (UTC)

I added your details to the current task. Elitre (WMF) (talk) 09:33, 31 January 2017 (UTC)

It just happened again, this time 605 KB ;)

It seems to be, that if I edit a section, get an edit conflict in there, and try to resolve it, the 2017WE thinks the section is the whole page and ditches the rest. Grüße vom Sänger ♫^(Reden) 17:13, 2 February 2017 (UTC)

Like, consistently? We're looking for ways to reproduce this, if this is one I can add it to the task. Elitre (WMF) (talk) 18:06, 2 February 2017 (UTC)

I never tried it again in the real world, as I feared it would happen again. This was the first time I dared, and voila, it struck again, so: yes, probably a pattern. Grüße vom Sänger ♫^(Reden) 18:08, 2 February 2017 (UTC)

As an answer to Anomie over @Phab:

Not that I know any daft thing about API, but your reasoning reads reasonable ;)

I just had an edit conflict while editing the whole page, and it jumped back to the normal editor, and the normal diff-view inside this for edit conflicts. Nothing was lost.

IIRC there was no such thing as the normal diff-view in the normal editor after the edit conflict while I edited just the section. Grüße vom Sänger ♫^(Reden) 17:46, 3 February 2017 (UTC)

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

Markieren eines größeren Textabschnittes/Tabellen kopieren Fehlerhaft

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.

---

Hallo,

beim markieren eines Textabschnittes, der über mehr als eine angezeigte seite läuft, kommt es beim neuen Wikitext Editor zu Problemen. Beim Markieren von oben nach Unten ist es nicht möglich, nur einen Teil nach unten zu ziehen. Sobald der untere Bildschirmrand erreicht wird, springt der Cursor zum Ende der Seite und markiert die komplette Seite ab dem Punkt, wo gestartet wurde.

Beim Markieren von Text von unten nach oben ist es noch kurioser: Starte ich irgendwo und markiere (ziehe also die Maus) nach oben und erreiche dann den oberen Bildschirm rand, springt der Cursor samt seite wieder zum asugangspunkt. Eine Markierung ist daher nicht möglich, es muss auf den alten Wikitext Editor gewechselt werden.

Weiterhin tritt beim einfügen einer kopierten Tabelle (des Quelltextes davon) das Problem auf, dass Leerzellen anscheinend nicht mit eingefügt werden. So verrutscht der Inhalt jedes mal. Da das kopieren einer Tabelle mit verbundenen Zellen auch im VE nicht funktioniert, muss auch hier wieder auf den alten Wikitext Editor zurückgegriffen werden.

@Elitre: Es wäre schön hier wieder phabricator Tasks erstellt werden könnten, ich bin dafür zu blöd.

Grüße

Hello,

there are some porblems in NWE when you try to mark text passages larger then one side. If you try to mark text from top to down, the Cursor will always jump to the end of the whole page if you reach the bottom of the current window, instead of Scrolling down slowly to stop at the Point you want to.

If you try to mark text from bottom to top, the Cursor will always jump to it's opening Position if you reach the Header of the text field/edit window. It's not possible to mark text with NWE if the passages are greater then one site.

Additionally, i tried to copy&paste a table from one Wikipedia Project to another language Version of it. The NWE deleted the empty cells. However, the connected cells were lost too. I had to Switch to old wikitext Editor to solve the Problem to paste it, save the page and edit it after that in NWE. There seems to be Problems by inserting the code.

@Eltire: It would be nice if you could start phab-Tasks for that, i am to dumb for that. sorry for this bad englisch, ask me anything if you have Problems understanding what i wrote xD

Best. Pearli (talk) 11:29, 31 January 2017 (UTC)

Sure, but I appreciate being able to provide specific examples - it makes it easier for others to try and replicate. Elitre (WMF) (talk) 15:22, 1 February 2017 (UTC)

Ok, lets suppose you want to edit the site https://en.wikipedia.org/wiki/Overwatch_(video_game)?veaction=editsource#Accolades on english wikipedia. If u try to mark a big text pasage like the first two sections from bottom up to top, the browser always jumps to the cursor position where you started. It is not importand which text passages you want to mark. It happens to all, with and without wiki-syntax.

The 2nd thing, top to down, is a bit harder, it didn't jump to the bottom of the page, it is hopping large, large text passages down. You can't really do accuracy work if this happens. It is a bit frustrating and i switched to old wikitext editor to "solve" the problem and switched back after i finsihed my work.

I hope it's more clear now, if you need a video to get necessary information, i can upload on later that day. Thanks a lot. Best Pearli (talk) 15:49, 1 February 2017 (UTC)

This is now https://phabricator.wikimedia.org/T157291. I'd love to learn more about your Phab challenges though. You don't even need a separate login for that. Elitre (WMF) (talk) 10:12, 6 February 2017 (UTC)

The editor is also making weird jumps for me, in particular when trying to shift+select text with keyboard or pasting text in mobile, it sometimes will randomly jump to the start of the line.

I cannot reliably reproduce it, so I can't produce a clearer bug report; but the editor should never move the cursor insertion point automatically, that's always unexpected behavior. Diego Moya (talk) 11:42, 31 January 2017 (UTC)

A first solution is to hold down the left mouse button and use the middle mouse button to scroll up or down. That seem to work for me. But it isn't really comfotable. Best Pearli (talk) 10:56, 6 February 2017 (UTC)

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

possible to implement syntax higlighting?

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.

---

Hallo,

wäre es möglich, wie das Skript wikEd eine native syntax-Hervorhebung einzubauen? Das würde das Bearbeiten um einiges angenehmer machen.

Grüße

Hello,

is it possible to implement native Syntax highlighting to NWE like the script wikEd? It would be great for editing the code with highlighted code Areas. Thanks for your help.

Best. Pearli (talk) 11:32, 31 January 2017 (UTC)

Yes, syntax highlighting is mentioned in the very page describing this project as a nice-to-have. The team is looking into ways to allow people who want the feature to have it without degrading the experience for everybody else (a much, much larger group). There is some related conversation happening in https://phabricator.wikimedia.org/T101246 . Elitre (WMF) (talk) 13:18, 31 January 2017 (UTC)

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