Bug 112502 - Resizing custom file properties dialogue makes fields misalign/disappear
Summary: Resizing custom file properties dialogue makes fields misalign/disappear
Status: RESOLVED FIXED
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: UI (show other bugs)
Version:
(earliest affected)
5.4.1.2 release
Hardware: x86 (IA32) macOS (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: target:6.0.0 target:5.4.2
Keywords:
Depends on:
Blocks:
 
Reported: 2017-09-19 21:02 UTC by Fred
Modified: 2017-09-20 08:45 UTC (History)
0 users

See Also:
Crash report or crash signature:


Attachments
Zip of original dialog, once resized and twice resized (138.50 KB, application/zip)
2017-09-19 21:02 UTC, Fred
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Fred 2017-09-19 21:02:09 UTC
Created attachment 136382 [details]
Zip of original dialog, once resized and twice resized

Tested with Writer and Calc, but seems to be generic issue.

The custom properties dialogue doesn't leave much space to view field names or the data they contain, but both expanding as well as shrinking the dialog window shifts the property value fields upwards so field name and value no longer correspond. After repeating this a few times, the field values are hidden completely.

The locations only reset themselves when the entire properties window has been closed and re-opened, just switching tabs doesn't help.

I've attached some quick screenshots in the zip.
Comment 1 Adolfo Jayme Barrientos 2017-09-20 08:38:21 UTC
It should be better with this commit: https://cgit.freedesktop.org/libreoffice/core/commit/?id=14afb688d3a24be302867ea614b0e30e01d168be

Please try again when 5.4.2 is released :)
Comment 2 Adolfo Jayme Barrientos 2017-09-20 08:40:43 UTC
... And the dialog’s initial size was improved as well: https://cgit.freedesktop.org/libreoffice/core/commit/?id=507247697dc6c4a41fe17a29d522511f97040738 (this commit is 6.0-only, though).
Comment 3 Fred 2017-09-20 08:45:36 UTC
Wow - fastest bug resolve ever :)

Any chance you could find a way to squeeze feature request 112504 in there too before the caffeine runs out?  :)