Server address field in wizard lacks context menu

[i2h3]

This is a quick documentation for us to not let this slip through in 34.0.0.

The server address field does not offer any context menu. It is possible to paste text by using the keyboard shortcut for that but that cannot be expected from everyone. This is an accessibility issue.

Mentioning @Rello for awareness because he used to lead the related changes.

[Rello]

Hi,
what do you mean by context menu?

[i2h3]

what do you mean by context menu?

"Right click" in the text field. Conventional actions like cut, copy and paste are not available. Usually come for free for standard controls. 🤔

[claucambra]

@i2h3 I think the only way for us to handle this is to create a common textfield component that includes a menu and these menu options. Conventionally you'd create a custom theme and implement the menu in the themed version of the textfield, but we can't do that as we rely on the native styles for each OS

[Rello]

This is how it looked in the old wizard

[Rello]

#10398
wdyt?

[claucambra]

@Rello the old wizard used Qt Widgets which is a different technology. Indeed it offered full context menu entries for text fields.
Your solution works but I think it would be better to introduce context menus in some unified way across all

[Rello]

@Rello the old wizard used Qt Widgets which is a different technology. Indeed it offered full context menu entries for text fields. Your solution works but I think it would be better to introduce context menus in some unified way across all

not sure if i get it. you mean apply this not only to WizardTextField but also to all other text fields in the client?
there would be the search field in the search dialog and the assistant input field I could think of

[claucambra]

there would be the search field in the search dialog and the assistant input field I could think of

there are also text fields in places like the sharing UI
I think we would benefit from having the behaviour of these text fields be consistent

[Rello]

I agree.
all the separate dialogs will get a redesign anyway. Sharing will be done new for .1.
So this fixes a topic for now. I would suggest to take this as "better than nothing".

[claucambra]

I would suggest to take this as "better than nothing".

sure; if we need something that functions as a basic quick fix, I would suggest we create a base textfield component that implements the menu and then replace uses of the standard QtQuick Controls TextField with the new custom context-menu-supporting version. this should be trivial