<table><tr><td style="">colomar 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/D4838" rel="noreferrer">View Revision</a></tr></table><br /><div><div>
<blockquote style="border-left: 3px solid #a7b5bf; color: #464c5c; font-style: italic; margin: 4px 0 12px 0; padding: 4px 12px; background-color: #f8f9fc;"><p>Okay, personal opinion on why split buttons are among the most horrible things related to UX:<br />
(And whilst some of these points might not apply to this very specific use case here: they will elsewhere, and once one component users this button, others will too, see e.g. spectacle)</p>
<ul class="remarkup-list">
<li class="remarkup-list-item">They are very prone to accidental clicks. If you want to click the (little) arrow but hit the button instead, worst case you get an undoable, destructive action. This gets a lot worse with touch.</li>
</ul></blockquote>
<ol class="remarkup-list">
<li class="remarkup-list-item">You should not use a split button with the main button performing a destructive action, of course.</li>
<li class="remarkup-list-item">Plasma Desktop is not optimized for touch input, Plasma Mobile certainly would not not use them. And as you say yourself below, a context menu does not work for touch, either.</li>
</ol>
<blockquote style="border-left: 3px solid #a7b5bf; color: #464c5c; font-style: italic; margin: 4px 0 12px 0; padding: 4px 12px; background-color: #f8f9fc;"><ul class="remarkup-list">
<li class="remarkup-list-item">They are horrible for handicapped people. Screen readers usually don't handle them properly, so these people are only aware of one action, and might not be able to see the others</li>
</ul></blockquote>
<p>How do context menus work with screen readers?</p>
<blockquote style="border-left: 3px solid #a7b5bf; color: #464c5c; font-style: italic; margin: 4px 0 12px 0; padding: 4px 12px; background-color: #f8f9fc;"><ul class="remarkup-list">
<li class="remarkup-list-item">They are horrible for keyboard based navigation (see above on not applying for this very specific use case): which button presses them? Which one opens then?</li>
</ul></blockquote>
<p>Split buttons are usually used in toolbars, which are never good for keyboard navigation. That's what menu bars are for.</p>
<blockquote style="border-left: 3px solid #a7b5bf; color: #464c5c; font-style: italic; margin: 4px 0 12px 0; padding: 4px 12px; background-color: #f8f9fc;"><ul class="remarkup-list">
<li class="remarkup-list-item">Space. These buttons have text on them, text that is translatable and might be a lot bigger in e.g. German. The buttons in notifications already suffer from this (e.g. bluetooth received files, in German) and it only gets worse if you add multiple options and an additional arrow</li>
</ul></blockquote>
<p>Is that arrow really taking up that much space?</p>
<blockquote style="border-left: 3px solid #a7b5bf; color: #464c5c; font-style: italic; margin: 4px 0 12px 0; padding: 4px 12px; background-color: #f8f9fc;"><ul class="remarkup-list">
<li class="remarkup-list-item">They would obviously not work well with multiple items as per the example above, if you e.g. wanted item specific actions</li>
</ul></blockquote>
<p>As I said: Neither does the simple button. The split button wouldn't be the one crrating the problem. And it would not _replace_ the context menu, either.</p>
<blockquote style="border-left: 3px solid #a7b5bf; color: #464c5c; font-style: italic; margin: 4px 0 12px 0; padding: 4px 12px; background-color: #f8f9fc;"><p>What would work are either context menus as proposed (touch is going to be meh though, as I just learned that we can't properply do long press anywere) or a button that only has the purpose of opening a menu, e.g.: hamburger button.</p></blockquote>
<p>Nobody said anything against the context menus, the split button would just be an additional, more discoverable means to access the functions.</p></div></div><br /><div><strong>REPOSITORY</strong><div><div>R120 Plasma Workspace</div></div></div><br /><div><strong>REVISION DETAIL</strong><div><a href="https://phabricator.kde.org/D4838" rel="noreferrer">https://phabricator.kde.org/D4838</a></div></div><br /><div><strong>EMAIL PREFERENCES</strong><div><a href="https://phabricator.kde.org/settings/panel/emailpreferences/" rel="noreferrer">https://phabricator.kde.org/settings/panel/emailpreferences/</a></div></div><br /><div><strong>To: </strong>broulik, Plasma, VDG<br /><strong>Cc: </strong>mart, Fuchs, subdiff, colomar, plasma-devel, progwolff, lesliezhai, ali-mohamed, jensreuterberg, abetts, sebas, apol<br /></div>