| • MZMcBride | |
| Sep 16 2014, 11:49 PM |
| F14892: mmv-reuse-resized.png | |
| Nov 22 2014, 3:48 AM |
You can see attachment 16491 for reference.
As far as I can tell, the MediaViewer embed text area cannot be resized. I'm not sure why this is, but it's frustrating and annoying, particularly as the box is too small (bug 70914).
Version: unspecified
Severity: normal
See Also:
https://bugzilla.wikimedia.org/show_bug.cgi?id=70914
OOUI textInputWidgets have resize:none by default. We could override that, but given that the whole panel is fairly small and non-dynamic, I don't see much benefit.
(In reply to Tisza Gergő from comment #1)
OOUI textInputWidgets have resize:none by default.
I don't understand why this is. It seems to directly defy user expectations.
We could override that, but given that the whole panel is fairly small and
non-dynamic, I don't see much benefit.
Well, the whole panel shouldn't be so small and it is dynamic (the text area changes with drop-down menu selection changes).
Created attachment 16504
embed HTML textbox resized to show all text
(In reply to MZMcBride from comment #2)
OOUI textInputWidgets have resize:none by default.
I don't understand why this is. It seems to directly defy user expectations.
I am not familiar with the design decisions behind OOUI or how it is used in other products. OOUI has a separate bugzilla component, if you think this is a bug in general, you might want to file it there.
Well, the whole panel shouldn't be so small and it is dynamic (the text area
changes with drop-down menu selection changes).
The reuse panel has fixed size. I would rather not enable a resize handle if the user would end up like this after using it.
Attached:
I am inclined to close this in favor of bug 64713. I agree that it would be good to be able to read the text without copypasting it into a notebook. I think resizing is only valuable as a means to that end, and it is not even a very good means. A tooltip or autoexpanding or moving the panel to a more spacious location would be all better solutions.
(In reply to Tisza Gergő from comment #4)
I am inclined to close this in favor of bug 67835.
I think bug 70914 might be a duplicate of bug 67835, but perhaps not this bug (bug 70915). For it's worth, I very briefly spoke with Timo about the behavior of OOUI:
it's disabled because while it is a native feature that users may expect, it is too liberal. Like contenteditable it needs restrictions to work well or it'll destroy your layout. Especially horizontal resizing