Bug 121640 - The new character "features" assistant needs scroll bars for font with many OpenType/Graphite features
Summary: The new character "features" assistant needs scroll bars for font with many O...
Status: RESOLVED DUPLICATE of bug 122119
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: UI (show other bugs)
Version:
(earliest affected)
6.2.0.0.beta1+
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-11-22 20:47 UTC by RGB
Modified: 2018-12-19 10:33 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
The zip file contains two screenshots showing the problem (146.58 KB, application/zip)
2018-11-22 20:47 UTC, RGB
Details

Note You need to log in before you can comment on or make changes to this bug.
Description RGB 2018-11-22 20:47:50 UTC
Created attachment 146922 [details]
The zip file contains two screenshots showing the problem

On 6.2 beta 1, go to the character formatting menu and select a font with lots of OpenType/Graphite features. For example, Linux Libertine G. Now click on the new "Features..." button to see what the font offers. The behaviour depends on which VCL plugin you are using.

GTK3: a window that cannot be resized is presented with all the features the font offers, but as there are so many, the resulting window is taller than my screen so many options are not easily accessible.

KDE5: the window has a reasonable size, but it content cannot be "scrolled" so many options are completely inaccessible. Note that with the KDE plug-in it is possible to resize the window, but for a font with so many options, that ends up with the problem presented with the GTK3 plug-in: the window becomes bigger that the screen of some notebooks.

The "Features" menu should present a standard size and a scrollbar to show all the options offered by more complex fonts.
Comment 1 Xisco Faulí 2018-12-19 10:33:50 UTC
Hello,
Thanks for reporting this issue. This is a duplicate of bug 122119

*** This bug has been marked as a duplicate of bug 122119 ***