Aaaaand another edge case: What should the user see, when there are no parameters at all?

In T297773#7618888, @thiemowmde wrote:

I think we should merge the existing patch as it is, and then move the ticket back to the backlog.

While implementing this: What should happen, if no parameter is used and you hide the unused. Should there be some text or do we show an empty nothing :-D?

In T297792#7613095, @ECohen_WMDE wrote:

Hmm good points - I wonder if it's actually simplest to just remove the "all" so it would be ... Changes will be lost and cannot be undone. and ... Edits will be lost and cannot be undone. I'm not sure if the word "pending" is needed because I think edit or change implies that it's the new stuff only that will be affected. Pending actually implies to me that maybe there could be some other changes in addition to my recent changes, which might cause more confusion?

Maybe removing "all" is enough to make it a bit clearer. I would start there - will update the task description!

While reviewing this I stumbled a bit over All changes will be lost and cannot be undone.. Personally I would find it more clear if the text somewhat emphasizes on pending changes. Just to make clear, that the "original" values still remain.

awight moved this task from Done to Sprint Backlog on the WMDE-TechWish-XMAS-Sprint-2021-12-15 board.

Ah just saw that now ... any reason for that?

In T275123#7585707, @thiemowmde wrote:

I tested a lot of things. I don't think there is anything to do here. The moment I (temporarily) fix the issue in Parsoid as described above, everything works fine. I suggest to consider this done and not report a Parsoid issue, but wait until this appears in the wild. Which is unlikely.

@WMDE-Fisch, have you been able to spot any actual misbehavior? I can't really tell fro your comment.

In T270239#7603973, @Lena_WMDE wrote:

We no longer need this board.

The fix was applied and the issue was resolved on Github.

Soo I looked at the last available 25 daily test runs. Mostly it's random but two cases stood out:

It even works with an arbitrary number of newlines and space in between. I wonder if this is really used somewhere .... If done from scratch I would say, that newlines should be forbidden in parameter names. But if the system is currently allowing this in source code it should be made sure, that it does not break when your editing a page with VE or any other tool.

Ok this does not seem to make sense without JS anyways. Soooo is it relevant?

In T297945#7577538, @awight wrote:

"Probox" turns out to rely on https://meta.wikimedia.org/wiki/MediaWiki:Gadget-addMe.js . Of course, if we can get a gadget deployed to dewiki we can have all the fancy UI we want... but this was already ruled out for this year.

We'll for now not work on the progress bar. A third option to consider here would be disabling the Edit button as long as the dialog loads. This way users might get a better understanding, that something happens and will not start clicking several times. - This would be easy to implement.

2. The instructions are currently arranged in a way that makes it sound like you need to select a part with space first before you can move/remove it. That's only partially true. The selected state only matters when you continue pressing tab and navigate down to the toolbar. The toolbar buttons act on the selected part. But that's not what the ARIA description is about. Ctrl+Shift+Cursor and Ctrl+Del act on the focused part. No need to press space first. Selection doesn't matter. That would be confusing for a screenreader user as they can't easily see which element is selected the moment they press Ctrl+Shift+Cursor and Ctrl+Del. Instead the hotkeys act on the same element that contains the description where the hotkeys are mentioned, i.e. the focused element.
   • Because of this the ARIA description is almost always the shortest "Press Space to select the template.". This includes all parts of a multi-part template, as long as none is selected.

Summary: As of now the hotkeys almost always work (the only exception are the move keys on single-parts), but are almost never announced because of the 2 problems described above.

• The message "If known, enter undocumented parameter names. Note that only parameters known by the template will have an effect. You may find information about existing parameters on the template's page." should also get a link to http://www.mediawiki.org/wiki/Special:MyLanguage/Help:VisualEditor/User_guide#Adding_undocumented_parameters. While this message might appear together with the other message that talks about undocumented parameters, this is rare. Repeating the link seems helpful. @ECohen_WMDE, ok for you?

I guess this can be closed now. Please feel free re-open if there's anything remaining that needs to be taken care of.