Feature summary (what you would like to be able to do and where):
When using Codex, there currently seems to be no option to create a dialog window that I could maximize or minimize. In fact, I don't think I can resize it either.
https://doc.wikimedia.org/codex/latest/components/demos/dialog.html
- Maximization could work either by double-tapping/double-clicking the title bar (a common feature on PCs) or by using a separate button with a maximization icon.
- Minimization could either collapse the dialog to an icon (which would have to be provided in configuration) or to just the title bar. What is important is that any progress made in the task would not be lost or modified. In other words, the elements should be hidden, not removed.
This would become more important once T434356 is done (adding the ability to move the dialog).
Example of collapsing to a title bar:
Use case(s) (list the steps that you performed to discover that problem, and describe the actual underlying problem which you want to solve. Do not describe only a solution):
- Gadgets for taking notes (and needing to copy something into the window). This would benefit from maximization when I want to focus on writing a note, and minimization when I'm done. One such gadget collapses to an icon when you close the window, but it is not ideal (the icon is placed somewhat randomly on the side of the screen).
- Gadgets for tracking threats like the interceptor could be used in a collapsed stated as a companion, and you would only open it when new threat arrives (like a bad edit for review that might need to be reverted or removed).
- Writing about the current article when submitting a nomination (for deletion, for a medal, or for the Did You Know column). This can be a large window, and it might take some time to complete the task. You might want to minimize it to more easily re-read some fragments or check notifications or maximize it to focus (people have problems with focus these days).
- Cat-a-lot could benefit from using a more standardized solution for minimization.
Benefits (why should this be implemented?):
Maximization is probably only important on larger screens (desktops/laptops), so it is more relevant to editors than readers. Minimization could also work on mobile: e.g. an insert-link dialog pops up, I minimize it to copy some text, then maximize it to paste the text into the dialog.
Note that on PCs (and Macs), most windows can be maximized and almost all can be minimized (even modal windows). Also note that while readers tend to use mobile devices, active editors still tend to use desktop computers or laptops to edit Wikipedia.
For example, at the moment I see 73 mobile edits out of 500 actions (486 edits in total) on enwiki on RC (link below). That is about 15% mobile edits and 85% other edits (taking 486 as 100%). It is a random sample, but this is also what I hear from active editors at conferences: people do make edits and perform other actions on mobile, but these are relatively rare – typically when waiting for a train, etc., or when there are no other options for them. Most of the time active users use a larger screen on which windows are not taking the whole screen.
