There doesn't seem to way to disable the automatic signature. Can you provide me with step by step instructions with how to do that or add the feature to disable automatic signatures to this project?
Talk:Talk pages project/New discussion
There is stil the old "edit source" button on every page right... ? Why add another option to a user interface that is trying to simplify interactions, when there is already a way to achieve complex things in another way ?
When you copy any formatted text (page title, hyperlink, section title, username, etc.), format is apparently kept when you paste it, but if you switch mode or save, it just disappears... This is really annoying.
Even worse, when you copy a sentence in a WP article, if it contains an hyperlink, the whole sentence will not be saved...
Which editing mode are you starting in (visual or source)? Do you have the toolbar enabled in the source mode?
Actually, I only have this issue with Firefox on Windows 10. It's working fine with Chrome on Windows 10 and even with Firefox on MacOS.
I'm starting in source mode. Regarding the toolbar, I'm not sure. What does it look like?
While adding to a talk page I may have a whole lot of tabs open, including multiple talk pages, and need to refer to them to provide diffs etc. Previously, I could find my way back to the active editing because the tab (in Firefox) showed "Editing". Now it doesn't. Please consider fixing it so that the message in my Firefox tab shows me which is the tab I need to go back to to continue my talk page message. Apart from that the new system seems pretty good, thanks.
I wholly agree with this. It’s a real concern for users of other browsers too. I use Chrome mostly on desktop. It ought to be simple to fix, but I, too, find it hard to return to the relevant tab to continue editing. I raised this quite some time ago myself.
It should be possible to load the older code editor with this feature. This way it would be possible to use the single API to customise the top panel. For example currently there is Wikificator button missing on Ukrainian Wikipedia when using the tool as well as the buttons that I have added to myself in my own vector.js. It is also frustrating that even manually writing ?action=edit§ion=new opens the new editor. I like the feature itself, but this limitation makes it much less useful.
Hello. Here are the steps to reproduce.
- Start a new topic. In Source mode, key in or paste an HTML entity.
- Example 1 :
> - Example 2 :
[[Page#Tag <li> and…]]
- Example 1 :
- Switch to Visual mode.
- Come back to Source mode or save. Entities are now different !
- Example 1 :
> - Example 2 :
[[Page#Tag <li> and…]]
- Example 1 :
The latter leads to a bad display and a broken link, since the tag is interpreted as a list item.
Notice that [[Page#Tag <li> and…]] (Unicode encoding) is also converted into [[Page#Tag <li> and…]] with the same issue.
These inappropriate replacements don't occur with the older tool.
Unrelated remark. The present Structured Discussions (Flow) feature adds unnecessary ="" after the inline attribute in syntaxhighlight tags.
Best regards.
Normally when I (using Firefox on Mac) double click in a text box it has the effect of highlighting the word clicked on or the nearest word, or sometimes (if not on a word) all the text in the box. Double clicking in the reply text box does that if I'm clicking on a word, but if I double click in a blank space it takes me out of the reply box altogether – it remains open but with the icons greyed out and without me being able to type in it, the same as if I click outside of the box. Triple clicking usually always highlights all the text, but in the reply tool always has this unwanted effect. The double click might not be too much of a problem, but not being able to select all with a triple click is more annoying, for me at least.
Do you get the same effect if you type a reply to me here (this page uses Flow)?
No, only on Wikipedia pages. Though actually, having updated Firefox (to 100.0.2) the issue seems to have gone away now.
If I start a new topic in source mode, and paste in code that generates a section title (e.g. using {{subst:requested move}}), I get the "Please provide a title for your discussion topic. If you click "Add topic", your topic will be added without a title" error. Might it theoretically be possible for the tool to detect whether I've included such code and not prompt me to add an unnecessary second section title?
Maybe? We can always ask the devs, and they'll figure out whether it's possible. I'll get a bug number for you, and post it above.
The "Insert" and "Cite" options in the main toolbar do not exist in the new discussion tool, and this is not good.
please add these options to New discussion.
Thank you for your suggestion. Can you show me an edit that you needed these tools for? Which items in the Insert menu do you want to use most often?
The "Images and Media" and "Template" options will be most useful, although other options are also useful.
Thanks for this information.
There are some technical challenges around templates in replies (though not when you're starting a ==New section==). "Inline" templates (like {{citation needed}} are okay, but a "block formatted" template (e.g., most infoboxes) will corrupt the page, because a : will be added before each line of the template. @PPelberg (WMF), I think we should look into this problem with templates again. At minimum, we could consider re-enabling the {{ keyboard sequence for tables in the new topic tool, where the problem doesn't appear. (By the way, Mohammad, if you type <ref in the visual mode, it will open VisualEditor's cite tools for you.)
How often do you add images to a comment on a talk page?
Thank you, It will be easier if their buttons are added.
Once every few months, but mostly to report an error or question.
I use the desktop site on mobile. To be precise, I use chrome browser in One UI 4.0. However, when I copy and paste, the pasted content doesn't seem to be recognized. (If the Add button is not activated and try to enter additional text, only the entered text is displayed.) The 2017 wikitext editor seems to have the same symptoms. Sorry for bad english.
Are you trying to copy/paste formatted text (such as links)? Does this happen even if you copy/paste a single word of plain text?
(Your English is good. If you would rather write in another language, that's okay. MediaWiki.org is a multi-lingual wiki.)
Perhaps the symptom only appears when using some wikitext (eg *, {{}}). Copying plain text doesn't cause that symptom.
Can syntax highlighting be added at the source mode of the reply tool? I don't know why that hasn't been implemented yet...
This should be feasible, from a technological perspective, but it has not been a common request.
What do you think of the live preview in source mode?
The live preview mode is great (you don't have to spam the "preview" button). But maybe add the ability to hide/show it for a cleaner experience?
I usually use the visual mode myself, so I don't see the live preview. Do you find it distracting or something?
It can be (somewhat) distracting (I was confused once on why nothing works, then I remembered that I was clicking on the live preview), so I guess a toggle could be great.
Maybe add an option to reposition it to the top (like on normal source), since I'm used to scrolling to the very bottom of the page to see the editor area.
So far, in the Reply tool, the team has been prioritizing having the editing box as close as possible to where your comment will appear on the page. Putting the live preview above the box would separate the editing box from the previous comments. If you posted a long comment, you might not be able to see the previous comments on your screen (because the live preview would take up so much space). Do you think that would be okay?
Eh.... I don't know... But I guess no?
(But maybe have the option to hide it altogether.)
Now that I think about it, maybe add an option to reposition it to the side instead?
I'm not sure that would work very well for people on smaller screens, especially when the comment is heavily :::::::::::indented. But just knowing that it's currently sub-optimal is useful, even if the solution isn't obvious yet. Please feel free to keep thinking about ideas – the team really does want to hear your thoughts. You've suggested several good areas for them to explore.