<html>
<head>
<base href="https://bugs.documentfoundation.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Useless scrollbar for Gradient / Bitmap / Hatch fill selection"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=120036#c5">Comment # 5</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Useless scrollbar for Gradient / Bitmap / Hatch fill selection"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=120036">bug 120036</a>
from <span class="vcard"><a class="email" href="mailto:momonasmon@gmail.com" title="Maxim Monastirsky <momonasmon@gmail.com>"> <span class="fn">Maxim Monastirsky</span></a>
</span></b>
<pre>(In reply to Tamás Zolnai from <a href="show_bug.cgi?id=120036#c0">comment #0</a>)
<span class="quote">> Actual Results:
> There is a scrollbar for the list, but it has no function.</span >
It's intentional. See the comments in <a href="https://gerrit.libreoffice.org/28492/">https://gerrit.libreoffice.org/28492/</a>
(In reply to Caolán McNamara from <a href="show_bug.cgi?id=120036#c4">comment #4</a>)
<span class="quote">> caolanm->maxim: what case was the above for example, is it the palette in
> the color dropdown case ?</span >
Yes it is. There was also a recent case with a ColorValueSet inside a dialog -
see <a class="bz_bug_link
bz_status_VERIFIED bz_closed"
title="VERIFIED FIXED - UI: Layout shifting a little when opening the Color dialog in Table properties Background"
href="show_bug.cgi?id=119299">Bug 119299</a>.
IIRC The problem is that it's a common practice to call stuff like
ValueSet::CalcWindowSizePixel from an outside code, and set its output as a
size request for the control (e.g. see ColorValueSet::layoutAllVisible usage
inside the ColorWindow ctor). But in the welded world, the size request is set
to the drawing area, and the scrollbar width comes from a separate scrolled
window. Which means that if we don't have overlay scrollbars, the drawing area
needs to be enlarged when we don't want to show the scrollbar. But this
shouldn't happen if the previous size request was a result of such external
CalcWindowSizePixel call, as it already detected the uselessness of the
scrollbar, and gave a larger area. Otherwise this will result in the scrollbar
width being calculated twice.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>