Page MenuHomePhabricator

[PageMigration] Text areas constant heights are not helpful
Open, MediumPublic

Description

Example of badly used vertical space on Special:PageMigration

Niklas hated the scrollbars in the small text areas, while migrating a https://www.mediawiki.org/wiki/Manual:LocalSettings.php translation.

In my case, the problem is rather that so much vertical space is wasted and I have to scroll the page a lot in order to cut and paste text from one textarea to another. Some ideas for improvement that I throw for consideration:
a) adapt the height to the space required by the source text, keep it constant for the corresponding text area on the right side;
b) allow to move the division between right and left for all the textareas at once, not only one by one, so that I can gain more horizontal space if I want;
c) if it doesn't disrupt things too much (or when the changes above allow it), don't add scrollbars but always fit the height to what's actually needed to fit all the text.


Version: master
Severity: normal

Attached:

PageMigrationHeights.png (900×1 px, 53 KB)

Details

Reference
bz69308

Event Timeline

bzimport raised the priority of this task from to Medium.Nov 22 2014, 3:32 AM
bzimport set Reference to bz69308.

Content translation uses an algorithm to fit both columns to minimum height without scrolling.

pr4tiklahoti wrote:

(In reply to Niklas Laxström from comment #1)

Content translation uses an algorithm to fit both columns to minimum height
without scrolling.

Alright, we can adapt to the logic used over there. But I think its better to do these enhancements once GSoC is over. Because, apart from developing a logic similar to the one used at content translation, we would also have to make changes to the code related to adding and deletion of a new unit. Also, the h2 patch results into collapsing of some units into one. So, we also need to take this into consideration - imagine a large chunk of collapsed units in a textarea having height of just 3 rows because it got aligned with a section header. Quite a lot of issues to be considered there. But, I will only work on it and come up with something better. :-)

@Nemo_bis: Is this obsolete as Special:Translate only "opens" one translation unit anyway these days? Or what is being asked for nowadays?

@Aklapper This task is about Special:PageMigration, not Special:Translate. Special:PageMigration still uses a two-column layout; actually basically the only thing that changed in the past seven years is the icons, which became OOUI and got reordered:

Screenshot 2022-02-16 at 02-43-49 Translation page migration - Wikimedia Commons.png (706×1 px, 89 KB)

Ah, thanks. It's obviously a page I wasn't aware of.