Talk:2017 wikitext editor

Jump to navigation Jump to search

About this board

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

[resolved] syntax highlight support for other skins

3
Franklin Yu (talkcontribs)

I prefer Skin:Timeless over Vector (legacy or new); is there any plan to bring this editor to Timeless as well?

Edit: I realized that the editor works in Timeless, but the syntax highlight doesn’t. This is quite a deal breaker; I updated the title of this conversation.

TheDJ (talkcontribs)

It doesn't? It works for me... can you be more specific ?

Franklin Yu (talkcontribs)

I guess there was some caching issue on my browser. I restarted it and it works for me.

Liege (talkcontribs)

I like this one better but I miss the edit toolbar.

Whatamidoing (WMF) (talkcontribs)

The 2017 wikitext editor has an edit toolbar. It looks like this:


What do you miss?

Reply to "Edit toolbar"

2017NWE's workboard not well organized

7
George Ho (talkcontribs)
MGChecker (talkcontribs)

I think most of them are already on the VisualEditor main project workboard?

Anyway, I think you should feel free to categorize using workboard columns. However, most tasks are about the wikitext editor and would make a huge column anyway.

Jdforrester (WMF) (talkcontribs)

Please do not encourage people to re-organise the work boards of projects that are actively supported by other people without waiting for those owners to comment first.

You're right, the Editing team currently does all its organising in the VE work board. I think it would add huge confusion and no value to create a split-brain approach to task management by also organising them in another place, but that would be something for them to comment on.

MGChecker (talkcontribs)

I think I have misunderstood here. I thought George was talking about the BetaFeatures project workboard, which has a single column noone cares about and would be more useful split up. For this project, I do not think there would be a problem.

However, if this was about some VisualEditor workboard, I apologize for my misjudgement.

George Ho (talkcontribs)

No, you didn't misjudge. This topic is about the (beta) NWE project workboard, consisting of just one column, like you said.

MGChecker (talkcontribs)
George Ho (talkcontribs)

Then you were mistaken. :S

Reply to "2017NWE's workboard not well organized"

New category pages

2
Summary by Whatamidoing (WMF)
Deryck Chan (talkcontribs)

In the 2010 wikitext system, if you click on a category redlink, it gives you an empty category page to edit and at the same time displays what pages are currently in that category.

But in the 2017 wikitext system, if you click on a category redlink, all that appears is an edit box. Since categories don't show up on "what links here", there's no way to see what's in a category before you create a category page...! Can we have the category listing visible when we click on a category redlink?

Paucabot (talkcontribs)

I agrre with that feature. The workaround to see the categories is to delete some parts of the URL.

Reply to "New category pages"

How to activate a text editor

2
ErnaniMarques (talkcontribs)

How to activate a text editor that gives you edit html and texts in BOLD, Italic, etc?

Whatamidoing (WMF) (talkcontribs)

It sounds like you're trying to install a third-party wiki. If you want the "2017 wikitext editor", then it is part of Extension:VisualEditor.

Reply to "How to activate a text editor"
Omotecho (talkcontribs)

Please add translation tags to 2017 wikitext editor#See also sections. Better if Special:MyLanguage or any auto redirect type tag is added (sorry I forgot the terminology).

Shirayuki (talkcontribs)

YesY Done

Impossibility to put redirection on some Namespace

1
Summary by Elitre (WMF)
Nouill (talkcontribs)

Hi, I still don't understand why we can't put a redirection on some namespaces with the wikitext editor or the visual editor ? The problem exist since the creation of those editors, and it's very annoying for me to have to switch editor (I have to go to the Beta menu, desactivate the wikitext editor and reload the page, all times) when I need to put a redirection on a page on some namespaces, especially the Template or the Wikipedia namespaces.

Perhaps we can think that we're not usually put a redirection on this namespaces, but half my edit is merging page, so I pretty often have to put redirection on those namespaces.

Reply to "Impossibility to put redirection on some Namespace"
Summary by Elitre (WMF)

The fault is in the browser.

Quotengrote (talkcontribs)

In Internet Explorer IE 11.0.9600.18860 the syntaxhighlighting doenst work. Everytime i click an highlighted word the edit Windows scroll to the top. --~~~~

Elitre (WMF) (talkcontribs)

Extension:CodeMirror#Browser_support seems to say that yes, problems can still occur. I don't think I have found anything about this specific browser in Phabricator. Would you mind reporting either on the talk page for the extension, or Phabricator directly? Thanks.

Whatamidoing (WMF) (talkcontribs)
Quotengrote (talkcontribs)

Not anymore, my company has rolled out a new Version of IE. --~~~~

Kghbln (talkcontribs)

... do I install this mode? Is there a configuration parameter, a software dependency, etc. ... I am asking since I did not find the docu.

Publish changes dialogue is confusing

3
Summary by Whatamidoing (WMF)
Grüner Flip (talkcontribs)

I really like the new editor but I quite confused about the 'publish changes' dialogue. The first thing I want to do after editing is to have a preview. I would like to have a preview button next to publish. The publish dialogue itself has a confusing layout. Two button on top with 'resume' and 'publish', the edit comment area in the centre and 'preview' and 'review' at the bottom. 'Resume' is nothing else than closing the dialog, normally called 'cancel'. This can also be achieved with an X on the right top like in a normal dialogue. The UXD team has to decide if the want button on top or on the button of the dialogue, splitting the up is strange. The first time I opened this dialogue I didn't find the preview button because there is the edit summary beneath the 'resume' and 'publish' buttons and I didn't expect more button below the summary. The same applies to the 'Review your changes dialogue'. I think publish without preview shouldn't be so easy because editing the source code is always error prone.

TheDJ (talkcontribs)
Whatamidoing (WMF) (talkcontribs)

I think that the team agrees with you that this dialog needs some work. It was designed originally for the visual editor, where some things, especially the (non-)use of page previewing, are significantly different.

We can't use "Cancel" for the "Resume editing" button, because it makes people afraid that their changes will be lost (i.e., "Cancel the whole edit and discard all my work" rather than "Let me make one more change before I save my changes").

I don't think that any of the boxes in the visual editor have an (X) in the corner. The style documentation begins at OOUI. I believe that one of its sub-pages explains which buttons belong at the top (generally, the most commonly used ones) and which belong underneath.

Reply to "Publish changes dialogue is confusing"