Talk:Talk pages project/Replying/2021/03

The team would value any thoughts and/or questions you have about this new tool for Replying to specific comments on talk pages.

Editing text of pings

Tracked in Phabricator
Task T276143

Two, I think related, "bugs" about pinging in visual mode:

1. I type @Levivich, for example, but then I cannot remove the @ from "@Levivich" without removing the entire ping (with either the delete or backspace keys, nor can I select the @, or any part of the ping text, with the mouse; I can only select the whole ping text). I have to switch to source mode to do it. (This is also true for this page.) So if I want to refer to someone inline, I cannot refer to them without the @ sign remaining in the text.
2. There seems to be no way to edit the ping text, e.g. to pipe the link the way you can with regular wikilinks, so it has to be @Whatamidoing (WMF), there's no way to render that as "@WAID". (Sorry to use you as an example WAID.)

I think it would be better if it was possible to edit the ping text, in order to remove the @ and also to change the link label (pipe the link) when desired. Levivich (talk) 18:17, 1 March 2021 (UTC)

Both of these were possible in the early days, and I'm not sure exactly what changed. It might be a consequence of better support for RTL languages (because the equivalent of "Levivich@" looks weird). I've filed a bug report. Whatamidoing (WMF) (talk) 18:42, 1 March 2021 (UTC)

Hmm, it is a good idea, because in the Czech (cs) language we have declension. Example: "Jmenuje se Dangit" (He is Dangit) but "Dangite, jak vytvořím šablonu?" (Dangit, how can I create a template?). If I pick my username (Patrik L.) and someone wants a reply to me, he/she cannot easily use only my first name (Patrik). Patrik L. (talk) 20:02, 1 March 2021 (UTC)

Detect changes in the section and allow to reload the content

Tracked in Phabricator
Task T254116

Tracked in Phabricator
Task T250295

When I am replying to a sentence in a section, it should detect and inform me that the section has been updated and allow the content to be reloaded. There may be updated information that needs to be considered. YFdyh000 (talk) 14:59, 3 March 2021 (UTC)

Adding templates in New Discussion tool Visual mode

I like it that the Visual mode in New Discussion handles templates, wikitables, pre, etc. that were created in Source mode (which can't be used in Reply Tool until there’s markup for multi-line list items ... well, templates could, if there was some way to flag in TemplateData which ones are single-line safe).

I noticed that some VE magic text like ‘[[‘ and ‘<pre>‘ activates the corresponding edit cards, but ‘{{‘ doesn’t. Instead I get the message ‘wikitext markup detected ... switch to source mode’. Pelagic (talk) 20:56, 3 March 2021 (UTC)

Hmm, I noticed one interest thing. Go here and copy one of the templates (listed in the table after "Indikátory"). Then try to reply to any comment and paste copied template in VE. It works until I switch to a source mode and back to VE. Patrik L. (talk) 21:06, 3 March 2021 (UTC)

The {{ key sequence (the devs assure me that a key sequence is importantly different from a keyboard shortcut) used to work, but was disabled when they turned off template insertion in the visual mode. I expect the key sequence to be re-enabled whenever the RFC about multi-line comments is finally handled.

BTW, if you two are interested in that RFC, then the draft is at User:PPelberg (WMF)/sandbox. I'll ask @PPelberg (WMF) about it the next time we talk. Maybe we can at least get the draft moved to the mainspace here, so that people can start putting it on their watchlists. Whatamidoing (WMF) (talk) 21:13, 6 April 2021 (UTC)

Seems great, thanks

I activated it today on French Wiktionary, and didn't encountered any issue. I especially like the fact that it's possible to switch from VE and wikicode while keeping a visual rendering is excellent.

I see that models are not yet available in VE mode, but the notification message is clear, well done.

Here are some additional feature I would love: - in wikicode edit mode, option to show the rendering side by side with the wikicode, rather than a top/bottom layout - possibility to switch to "edit section wikicode" while keeping what was typed so far. Not a big deal, as the wikicode can be copied and pasted, but it would be fine to avoid this additional step and the "are you sure you want to leave this page, all changes will be lost?" message.

Have you been through accessibility tests? Psychoslave (talk) 22:04, 11 March 2021 (UTC)

Have you been through accessibility tests?

If you mean keyboard and screen reader accessibility, then there are a few known issues: T271773, T274423. We'd appreciate feedback on this, especially if you use a screen reader regularly. We neglected keyboard accessibility a bit, because bug T172694 made it impossible to leave the editor area using only the keyboard (in visual mode), but that is fixed now, so we can test other improvements more easily. Matma Rex (talk) 22:35, 12 March 2021 (UTC)

Thank you for the feedback with the precise hints to the relevant tickets. I greatly appreciate it.

I don't use a screen reader, and have no particular accessibility requirements personally. I'm careful on this topic purely because I desire that knowledge becomes as widely accessible as possible to all human beings. I can ask for feedback in canals that I know as including people with such a profile though. Psychoslave (talk) 05:13, 13 March 2021 (UTC)

Hey @Matma Rex, I was able to get a reply from someone who uses a screen reader, after a message on April’s accessibility mailing list. We talked by phone and it appears that actually even consulting Wikipedia (in French) is quite a big challenge. Luckily we live in the same city. So we planned to meet next week, and that way I will be able to help better and better understand this difficulties.

If you have particular recommendations on how to conduct this test session, or know someone or some documentation I should consult before this meet up, please let me know. The better I'm prepared, the more useful feedback I'll be able to give.

Cheers Psychoslave (talk) 13:36, 15 March 2021 (UTC)

Wow, I didn't expect that when I said we'd appreciate feedback, thanks! I'm curious to hear what they say.

I don't really have recommendations, sorry. If you're meeting with someone who's generally comfortable using websites with a screen reader, I wonder what they think about the general structure of the discussion – I would expect that the most difficult part of replying would be making sense of the nested lists used to indent comments (they're messy enough even if you're not sight-impaired), as well as the signatures, rather than actually submitting the reply.

I also wonder if they know about any of the keyboard shortcuts (in the editor and elsewhere in the interface), and whether they're be able to use the tools in the visual mode (poorly named, huh), like e.g. adding a link. Matma Rex (talk) 22:03, 16 March 2021 (UTC)

If you haven't used a screen reader yourself, it might be helpful to try one out. Windows and macOS/iOS both have basic ones built in (they're called Narrator and VoiceOver, respectively). Windows Narrator will show you a quick start guide, with the basic navigation commands, when you open it fo the first time. It's probably not the same software as they're using, but it at least follows the same concepts. Matma Rex (talk) 22:11, 16 March 2021 (UTC)

Hello,

Good to see that this kind of approach raises positive appreciations.

I can't promise you we will go as far as engaging in a discussion using this extension, since from my early feedback, it looks like even consultation might be a problem. But we will go as far as possible in testing interactions with a Mediawiki instance when you can only access it through screen reader.

Chances are good that it will be conducted with a FLOSS tool, since I found the person through the April mailing list, maybe Orca. For now I can't tell more, but will provide all relevant information I might acquire with the planned session.

Cheers Psychoslave (talk) 10:02, 17 March 2021 (UTC)

Hey @Matma Rex, I finally was able to take time to fill a report of the session we made Monday. Sorry for the delay. Accessibility of Wikipedia, a March 2021 use test session is on Meta. Please share your thoughts about it, here or on the talk page on Meta. Please let anyone you know as interested in the topic know that the page exists and that comments are welcome. That might help me to do better in future actions like that one.

Cheers Psychoslave (talk) 06:32, 26 March 2021 (UTC)

Pronouns

Tracked in Phabricator
Task T279483

Many times I need to check via {{GENDER:}} (or other tricky ways) the pronouns of a users (in english this is not a big deal, you can just use ''they'', but in italian, as in may other languages, this is not possible); would'nt be nice having instead of just "You are replying to <user>", "You are replying to <user> (<gender>)"? Valcio (talk) 13:01, 16 March 2021 (UTC)

I've noticed that a few of the translations of the "Reply to X" placeholder are written as "Reply to user X", that would probably be a natural-sounding way of hinting at the gender in languages where the word "user" has gendered forms (e.g. in Polish, "użytkownik" / "użytkowniczka"). I wonder if that's an option for Italian?

But the message does not actually allow {{GENDER:}} syntax. We should fix that…

Existing translations for reference: https://translatewiki.net/wiki/Special:Translations?message=discussiontools-replywidget-placeholder-reply&namespace=8

(A few other translations are written as "Reply to comment by X", including Polish, perhaps because translating it differently without access to {{GENDER:}} was too awkward.) Matma Rex (talk) 21:45, 16 March 2021 (UTC)

Feedback so far

Nice tool, thanks for creating. My feedback so far is: 1) Consider pre-filling the box with [[User:usernameGoesHere]] or similar, to trigger a ping. This is useful on mobile, where it is easier to delete a prefill than it is to type all that out. The user script reply-link does this on enwiki. 2) Keep an eye out for a bug where you put the cursor in one place, but when you type, the text goes in a different place. I had this happen on Android the other day, one time, but haven't seen it since. 3) If this tool is still not available in beta on certain wikis, consider documenting the following a little bit better, so people can opt in: if ( $( '#ca-addsection' ).length ) mw.loader.using( 'ext.discussionTools.init' ); . Again, great job. –Novem Linguae (talk) 14:42, 16 March 2021 (UTC)

This is absolutely the top feature needed! Especially for newer users who'd benefit from talk page discussions but are not as wiki syntax savvy. I am very happy with this! Shushugah (talk) 16:44, 16 March 2021 (UTC)

I just filed phab:T290198 about the interaction between pinging and Talk pages project/Notifications. That detail will hopefully get fixed, but more generally, I wonder if we will someday ping people a lot less often. If everyone's already getting a notice about every discussion, then why would I bother pinging them?

If you haven't played with the notifications system yet, then go to Wikipedia:Village_pump (technical)#dtenable testing and click the [subscribe] button. Whatamidoing (WMF) (talk) 19:29, 1 September 2021 (UTC)

Bug - highlight in wrong place

When submitting a post, it normally adds your reply to the page, and highlights it for 5 seconds. In this particular case, the highlight added several hundred pixels of padding to the bottom of the page, and highlighted in the wrong place. Best explained with a screenshot:

https://imgur.com/a/0WbAxd5

Here's the diff:

https://en.wikipedia.org/w/index.php?title=Talk:Sun&diff=1012503877&oldid=1012503422&diffmode=source

Also, if you'd prefer I place these bug reports somewhere else such as Phabricator or GitHub, let me know. Thanks. –Novem Linguae (talk) 18:48, 16 March 2021 (UTC)

I've seen this, too. What's your web browser? (I mostly see it in Firefox.) Also, do you mostly see it on pages with a collapsed section? There are several collapsed WikiProject tags at the top of that page. I've wondered whether the amount that it's offset is the same as the size of the collapsed section (that is, the size it would be if it weren't collapsed), but I haven't actually checked. Whatamidoing (WMF) (talk) 18:54, 16 March 2021 (UTC)

Interesting theory about the collapsed sections being the cause. First time I've seen this so not sure. I was going to guess that maybe replying at the bottom of the page had something to do with it. Windows 7, Chrome, 1080p. –Novem Linguae (talk) 19:09, 16 March 2021 (UTC)

Feedback

I just tried this out and overall it seems pretty cool.

The thing that is likely to stop me from using it is the live preview. I find it hard to concentrate when things are happening elsewhere on the page while I'm typing and I feel under pressure to do things like finish inserting characters for formatting before the preview updates to avoid e.g. temporarily making the entire text bold. I would much prefer to have a preview button (and ideally also a key shortcut) for triggering it manually when I'm ready to see a preview. Maybe the automatic preview could be made optional? Nikki (talk) 12:18, 17 March 2021 (UTC)

Nikki, have you tried out the visual mode? It doesn't have a separate preview, and I like its automatic search system for linking to pages and users. Whatamidoing (WMF) (talk) 20:02, 18 March 2021 (UTC)

I'm aware of the visual mode, yes. It's almost unusable on Wikidata (it doesn't support templates) and I want to use the source mode anyway.

Another issue: I typed "{{Q" in visual mode and something briefly popped up (ignoring my "prefers reduced motion" preferences) in the corner of the screen (nowhere near where I was typing) and was gone again before I could read what it said (inaccessible). Nikki (talk) 08:47, 31 December 2021 (UTC)

I haven't been able to find anything in MediaWiki preferences about reduced motion. How do you expect messages to appear? Whatamidoing (WMF) (talk) 20:24, 28 January 2022 (UTC)

Aweful

Tracked in Phabricator
Task T278466

New option has done inconvenient to link to articles! В.Галушко (talk) 17:44, 17 March 2021 (UTC)

Can you be more concrete? Patrik L. (talk) 18:30, 17 March 2021 (UTC)

Hi! I assume the complaint has to do with all the variety of tools and means that are available in the standard editor, that suddenly become unavailable for the experienced users "thanks" to the "New section" change. I, personally, don't like being limited in those means while creating a new topic, so there should be a way to disable that (part of the) feature for those who prefer more formatting options while wishing to keep the new replying functionality. Piramidion (talk) 06:10, 20 March 2021 (UTC)

Piramidion, at least at the moment, if you click "New section" while on the History page, you'll get your old wikitext editor. It's kind of a strange workaround. The team is talking about what should be in the toolbar, so if there are specific buttons/tools you want, please share your suggestions.

В.Галушко used the wikitext source mode for the New Discussion, which I believe has no buttons at all. There is a button for links and pinging editors in the visual mode. Whatamidoing (WMF) (talk) 20:31, 22 March 2021 (UTC)

Thanks. I, personally, wouldn't mind to have this feature (to start smaller topics) provided that there's a quick way to go to the standard wikitext editor (if I need to, say, organize a discussion of a new policy or guideline, or simply to start a new topic with a large chunk of explanatory text). Piramidion (talk) 07:42, 23 March 2021 (UTC)

Thanks, I've switched off that option on the Preferences. В.Галушко (talk) 20:40, 22 March 2021 (UTC)

It's stuck on for me

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 think. Unless I'm missing the setting. On en-wiki, I wiped my common.js, and I unchecked Preferences -> Beta features -> discussion tools, and hit save. Did this a couple of times, as I recall that saving preferences has been buggy in the past. I also hard refreshed a couple of talk pages (Ctrl-F5). Talk pages project is still on. Any tips? Thank you. –Novem Linguae (talk) 01:17, 18 March 2021 (UTC)

Actually the common.js-based enabling sets a cookie—this cookie remains even after you removed the common.js part, until it expires. You can put

mw.cookie.set('discussiontools-tempenable', null)

in your common.js, load one page and after that it can be safely removed (or you can use your browser console if you’re familiar with it, or any other method to remove the cookie named enwikidiscussiontools-tempenable). Tacsipacsi (talk) 02:18, 18 March 2021 (UTC)

That worked flawlessly. Thank you very much. –Novem Linguae (talk) 02:35, 18 March 2021 (UTC)

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

Missing toolbar in source mode

Prototype is here (and yes, Patchdemo is slow, it is only protoype).

Tracked in Phabricator
Task T257391

I noticed that the source mode in new talk page reply UI has missing the toolbar and it's less useful than Visual mode. It's very odd that source mode doesn't share an important element from Visual mode. Ijoe2003 (talk) 06:42, 24 March 2021 (UTC)

Update:

If you want to try out the toolbar for the wikitext 'source' mode, go to the end of Special:Preferences#mw-prefsection-editing on your home wiki and tick the box for "Enable editing tools in source mode" Whatamidoing (WMF) (talk) 19:30, 12 May 2021 (UTC)

Replying to deletion discussions

Tracked in Phabricator
Task T259865

Please see Wikipedia:Miscellany for deletion/Draft:Endeavor Business Media where I replied to the original nomination. Unlike Reply Link (Enterprisey's script) I did not get the the chance to reply to the discussion per se, but chose to use intelligent indenting to place an indented reply below the comment left by the editor who nominiated the draft for discussion, at the foot.

I am content with this comment's indentation by happenstance and good fortune, but normally would not haven

You wight wish to set up dummy AfD and Mfd discussions to test behaviour in them. I acknowledge that thsi is Beta. Timtrent (talk) 08:11, 26 March 2021 (UTC)

I think setting up dummy discussions may be beyond me! Timtrent (talk) 20:19, 3 October 2021 (UTC)

The Reply tool currently doesn't let you change the indentation level. The team hopes to add that feature in the future. Whatamidoing (WMF) (talk) 20:23, 5 October 2021 (UTC)

Feedback from dewiki

Hi, in the last days I collected some feedback from using the tool at dewiki. I know some of the following points are already known and have a phabricator task, but I still want to mention them to indicate that these issues also came up on our project.

Already known:

• Don't show reply links on archives and pages which are not designated for further discussion (per NONEWSECTIONLINK): phab:T249293
• Dont't show reply links on pages you can't edit because of protection: phab:T276393
• Toolbar in source mode is missing: phab:T257391
• Missing possibility to define watchlist expiry: phab:T278190
• Restrictions on visual mode: Help:DiscussionTools/Reply tool visual mode limitations
• Editing (at least your own) comment afterwards: phab:T245225

And now some (I guess) new points, please excuse if there are any already being discussed:

• We use editMenus as a standard gadget on dewiki as the replacement for MediaWiki:Onlyifediting.js and mw.toolbar. This adds a bar with special characters below the wikitext editor (see screenshot on the gadget's page). It would be nice and consistent to have this one also while replying. The maintainer of the gadget said that he needs a hook being fired when opening the reply tool for adding the bar, because currently it is only loaded at page load once for all visible edit boxes.
• Reply links also show up in templates that (for example) indicate when a discussion is closed. On dewiki we use :de:Template:Erledigt which requires a signature for the archive bot. Currently the reply link is shown inside the template and could lead unexperienced users to reply to the topic even though it's marked as closed (no further replies wanted). Maybe you could introduce a css class indicating elements in which signatures should not get a reply link.
• The standard wikitext editor uses syntaxhighlight with CodeMirror. I don't know if it's possible to adapt to the reply form, but would make handling of wikitext more consistent.
• It is currently not possible to mark your reply as minor change
• There is no space added between colon and reply text, could make the source harder to read while editing the page in a normal way

A personal note from me at the end: I think this is the best new feature since years and finally an approach to simplify discussion pages without breaking the workflow of experienced users. So thank you very much for your effort. And as you can see on the Kurier page, the dewiki community is not always rejecting changes ;) hgzh 16:22, 26 March 2021 (UTC)

I am the one mentioned as maintainer of the tool permitting insertion of special characters and even more sophisticated things, like enclosing the currently selected text etc.

• Many wikis have similar tools for more than a decade, like editTool or whatever, heading for source code.
• There should be a common interface for all those gadgets:
  • mw.hook( "DiscussionTools.opened" ).fire( $wrapper );
  • Transferring a $wrapper or DOM with the block element where any insertion tool may be appended, typically below a textarea.

editMenus is able to feed character insertion on VE mode as well, not only source text mode.

• Therefore gadget developers will need two more hooks, for hiding toolbar or for changing insertion mode when toggled:
  • mw.hook( "DiscussionTools.source" ).fire( $textarea );
  • mw.hook( "DiscussionTools.visual" ).fire( ve.object );

I am really looking forward to see DiscussionTools growing and very helpful for new and occasional users. PerfektesChaos (talk) 17:03, 26 March 2021 (UTC)

While the hooks in my previous contribution are to be fired by DiscussionTools, it might listen to another one:

• mw.hook( "DiscussionTools.inhibit" ).add( finish );
• This one will be issued if the wiki does not like to apply DiscussionTools to certain pages with signatures.

There are local patterns for pages that are not supposed to receive comments, like straw polls or RfC or whatever.

• Kondolenzliste is a list of signatures if a German wikipedian has passed away. A list of condolescences, usually in user space, but should never happen to trigger talk page mode.
• Many other patterns are known locally, they will permit to open new sections, but not opening a conversation. Especially in project space. PerfektesChaos (talk) 17:46, 26 March 2021 (UTC)

@Hgzh:

• It is currently not possible to mark your reply as minor change

I don’t think it should be, either. According to m:Help:Minor edit, a minor edit is a version that the editor believes requires no review—a reply always requires review, why else would one write it? Fixing typos in one’s previous comment and the like are valid minor edits on talk pages, but they’re not (yet) available in DiscussionTools.

----

@PerfektesChaos:

While the hooks in my previous contribution are to be fired by DiscussionTools, it might listen to another one:

• mw.hook( "DiscussionTools.inhibit" ).add( finish );

If the CSS class proposed by Hgzh is not suitable and you want to disable the reply tool on the whole page instead, I think a parser switch like __NOREPLYLINK__ is a better solution, as it requires no JS, which means that

• no interface admin is required—smaller communities often have no interface admins, so the ability to configure DT themselves instead of relying on global interface editors is a huge difference;
• the reply tool can be disabled on server side—instead of adding the reply links on the server side and disabling them on the client side, the links are not added in the first place, so no unnecessary JS/HTML is downloaded and executed, and there’s no flash of the reply links. Tacsipacsi (talk) 19:02, 27 March 2021 (UTC)

@Tacsipacsi I don't think every reply requires review (by everyone). Imagine a discussion on a frequented talk page. User B helps user A who had a question on a side aspect in this discussion and A just replies thank you, B - it's a kind reply but not interesting for everyone else following the discussion, and could be skipped on their watchlists if wanted. But in general I think this can have quite low priority. hgzh 19:17, 27 March 2021 (UTC)

@Hgzh: A thank you message doesn’t require review, indeed—however, a minor edit still appears on watchlists, RC etc.; the thanks feature solves this problem better. I’d prioritize the ability to thank comments inline, with a button around the reply button (as opposed to thanking edits from the page history). Tacsipacsi (talk) 11:44, 28 March 2021 (UTC)

On parser switch like __NOREPLYLINK__:

• This would extend the entire Wikisyntax to support one feature of one particular tool on the old-fashioned talk page mode.
• A pattern recognition of pages with a certain naming scheme, e.g. names containing /poll or /archive or whatever in local language, can be applied to all pages without a need to change them. This can be maintained at central point.
• The __NOREPLYLINK__ approach would require that every user creating a page and all existing pages need to be equipped with this switch itself or a template providing that. That makes it more difficult for users to maintain those issues. PerfektesChaos (talk) 15:58, 29 March 2021 (UTC)

Copy paste text from previous comments, and keepwiki-links

I have really adopted this functionality, and use it constantly.

I miss one thing:

Very often I want to copy text from previous comments, to quote, but mostly to copy the wikitext; url:s and wikilinks for clarifcation (rather than saying "look above, it is somewhere in previous links" implying "you lazy S*B") and usernames (for pinging).

Now when you copy it becomes plain text.

• So, when hitting answer, if text marked and copied around the "answer-dialogue-box" would be wikiformated in the same way as it was when pasted into the answer dialogue, is missed.

I hope it is understandable what i miss, and I understand it is a lot to ask for. But does such a function make sense to anyone but me? To me it affects more than half of my answers, maybe more, mostly due to pinging where I cant use copy-paste. LittleGun (talk) 09:47, 27 March 2021 (UTC)

LittleGun, I think you're saying you'd like to copy formatted text and have it transfer still formatted? I suspect that would fight with another feature in Visual, which is to allow you to type formatted text and have it appear as typed, such as when you want to teach a newbie how to create a ping. In Visual, if you insert or type an existing page, it should offer to format as a wikilink for you. I haven't tried with a URL.

Maybe if Source allowed you to copy formatted text and when you pasted, it would reformat? Is that what you're looking for? Valereee (talk) 12:34, 27 March 2021 (UTC)

Yes, i want it to work as when copying text from visual editor editing: if I paste to a wikitext window it becomes wikicode. If I paste to a visual editor window it becomes formatted text.

I want copied text to keep its formatting. Now it becomes plain text. LittleGun (talk) 13:16, 27 March 2021 (UTC)

I tried the copying and pasting into the visual mode, and some basic formatting like links and bullet points are kept. (Other things like headings and images are lost, though.) Maybe it depends on the browser/operating system; I have Firefox 78 on Debian GNU/Linux 10 “buster”. Tacsipacsi (talk) 23:35, 27 March 2021 (UTC)

OK, thank you. What I am after is the links; for pinging, to refer and to quote.

If possible. (I am using Chrome on a Chromebook, mainly) LittleGun (talk) 17:39, 28 March 2021 (UTC)

As I wrote, copying and pasting links works for me right now. Do you have issues? Now I tried in Chromium as well, and it also works for me. (Chromium is Google Chrome’s completely open-source version, with hardly any difference between Chrome and Chromium, so if it doesn’t work for you, it’s more likely to be caused by the difference between Chrome OS and the Cinnamon desktop environment I use on Debian than the one between Chrome and Chromium.) Tacsipacsi (talk) 19:04, 28 March 2021 (UTC)

Yes, in a section-edit you can copy source from higher up in the edit box, but in Reply mode, the previous comments are HTML, so handling that formatting is useful. LittleGun, are you thinking of the “NWE” / “2017 wikitext editor”, where you can paste formatted text and it will ask do you want to convert to wikitext? There’s a prototype toolbar for Source mode which uses the 2017/NWE editor and offers that conversion. Paste formatted should already work in Visual mode. Pelagic (talk) 17:59, 5 April 2021 (UTC)