<table><tr><td style="">mart added a comment.
</td><a style="text-decoration: none; padding: 4px 8px; margin: 0 8px 8px; float: right; color: #464C5C; font-weight: bold; border-radius: 3px; background-color: #F7F7F9; background-image: linear-gradient(to bottom,#fff,#f1f0f1); display: inline-block; border: 1px solid rgba(71,87,120,.2);" href="https://phabricator.kde.org/D26530">View Revision</a></tr></table><br /><div><div><blockquote style="border-left: 3px solid #8C98B8;
color: #6B748C;
font-style: italic;
margin: 4px 0 12px 0;
padding: 8px 12px;
background-color: #F8F9FC;">
<div style="font-style: normal;
padding-bottom: 4px;">In <a href="https://phabricator.kde.org/D26530#593123" style="background-color: #e7e7e7;
border-color: #e7e7e7;
border-radius: 3px;
padding: 0 4px;
font-weight: bold;
color: black;text-decoration: none;">D26530#593123</a>, <a href="https://phabricator.kde.org/p/ngraham/" style="
border-color: #f1f7ff;
color: #19558d;
background-color: #f1f7ff;
border: 1px solid transparent;
border-radius: 3px;
font-weight: bold;
padding: 0 4px;">@ngraham</a> wrote:</div>
<div style="margin: 0;
padding: 0;
border: 0;
color: rgb(107, 116, 140);"><blockquote style="border-left: 3px solid #8C98B8;
color: #6B748C;
font-style: italic;
margin: 4px 0 12px 0;
padding: 8px 12px;
background-color: #F8F9FC;">
<div style="font-style: normal;
padding-bottom: 4px;">In <a href="https://phabricator.kde.org/D26530#592999" style="background-color: #e7e7e7;
border-color: #e7e7e7;
border-radius: 3px;
padding: 0 4px;
font-weight: bold;
color: black;text-decoration: none;">D26530#592999</a>, <a href="https://phabricator.kde.org/p/mart/" style="
border-color: #f1f7ff;
color: #19558d;
background-color: #f1f7ff;
border: 1px solid transparent;
border-radius: 3px;
font-weight: bold;
padding: 0 4px;">@mart</a> wrote:</div>
<div style="margin: 0;
padding: 0;
border: 0;
color: rgb(107, 116, 140);"><p>It would already be much better if the track was actually very visible, visually delimiting the space<br />
<a href="https://phabricator.kde.org/F7880630" style="background-color: #e7e7e7;
border-color: #e7e7e7;
border-radius: 3px;
padding: 0 4px;
font-weight: bold;
color: black;text-decoration: none;">F7880630: image.png</a></p></div>
</blockquote>
<p>I think it looks fantastic, or at least it would if that vertical line touched the top and bottom of the view, and the bar were wider so it did a better job of taking up the space in the track. This is in fact how macOS looks when you disable overlay-style scrolling globally, and personally I would like this everywhere -- at least on the desktop. On mobile, then sure, the scrollbars cam be tiny and almost/entirely disappearing. But I just don't like this style on the desktop. I don't think it's a case of, "it's new, I hate it." I'm pertty open to change, and I lived with it on and off on macOS since 2011 (see <a href="http://osxdaily.com/2011/08/03/show-scroll-bars-mac-os-x-lion" class="remarkup-link" target="_blank" rel="noreferrer">http://osxdaily.com/2011/08/03/show-scroll-bars-mac-os-x-lion</a>) but never got used to it.</p></div>
</blockquote>
<p>I may take a look into changing the breeze style do do such line, tough i would like that:</p>
<ul class="remarkup-list">
<li class="remarkup-list-item">breeze qwidget also supports disappearing scrollbar on touch (and hmm, configurable :p)</li>
<li class="remarkup-list-item">on mobile scrollbar behavior is always hiding, and overlay</li>
<li class="remarkup-list-item">even change on the fly when flicking a view with touch (and change back when the mouse is used): this is fine to be qml only as flicking is not really going to work correctly with qwidgets.</li>
</ul>
<blockquote style="border-left: 3px solid #a7b5bf; color: #464c5c; font-style: italic; margin: 4px 0 12px 0; padding: 4px 12px; background-color: #f8f9fc;"><p>I agree. However personally I think this impression comes from how typically each view is put within its own frame, rather than separating adjacent views with single-pixel lines like how Kirigami does it (which solves the problem). This leads to horrible frame overload like so: <a href="https://phabricator.kde.org/F7880807" style="background-color: #e7e7e7;
border-color: #e7e7e7;
border-radius: 3px;
padding: 0 4px;
font-weight: bold;
color: black;text-decoration: none;">F7880807: Screenshot_20200113_065712.png</a></p>
<div class="remarkup-code-block" style="margin: 12px 0;" data-code-lang="text" data-sigil="remarkup-code-block"><pre class="remarkup-code" style="font: 11px/15px "Menlo", "Consolas", "Monaco", monospace; padding: 12px; margin: 0; background: rgba(71, 87, 120, 0.08);">I don't think the size of the scrollbars has much to do with it.</pre></div></blockquote>
<p>yes, i'm saying that the patch besides putting the separation in the frame, it also reintroduces the frame by default, which is unrelated (and i think it should be avoided)</p></div></div><br /><div><strong>REPOSITORY</strong><div><div>R858 Qt Quick Controls 2: Desktop Style</div></div></div><br /><div><strong>REVISION DETAIL</strong><div><a href="https://phabricator.kde.org/D26530">https://phabricator.kde.org/D26530</a></div></div><br /><div><strong>To: </strong>ahiemstra, Plasma, Goal: Consistency, mart<br /><strong>Cc: </strong>kmaterka, mart, ndavis, IlyaBizyaev, ngraham, broulik, plasma-devel, LeGast00n, The-Feren-OS-Dev, jraleigh, zachus, fbampaloukas, GB_2, ragreen, ZrenBot, alexeymin, himcesjf, lesliezhai, ali-mohamed, jensreuterberg, abetts, sebas, apol, ahiemstra<br /></div>