<html>
<head>
<base href="https://bugs.documentfoundation.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED WONTFIX - Allow multiselecting for styles in Sidebar"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=139824#c2">Comment # 2</a>
on <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED WONTFIX - Allow multiselecting for styles in Sidebar"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=139824">bug 139824</a>
from <span class="vcard"><a class="email" href="mailto:mikekaganski@hotmail.com" title="Mike Kaganski <mikekaganski@hotmail.com>"> <span class="fn">Mike Kaganski</span></a>
</span></b>
<pre>(In reply to Heiko Tietze from <a href="show_bug.cgi?id=139824#c1">comment #1</a>)
<span class="quote">> Multi-selection is pointless for styles since you can do batch operations
> per hierarchy. If the document contains badly organized styles, meaning the
> mentioned 1000 all under Default, it's a user fault. => WF</span >
I disagree. Removing styles is not something about "operations per hierarchy".
And having 1000 styles is *not* a user fault, since it may come from import of
an external format, which user can't control, but that is perfectly normal use
case.
<span class="quote">> Multi-selection brings us to other challenges such as <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED WONTFIX - Highlight button sticks"
href="show_bug.cgi?id=55457">bug 55457</a>.</span >
Was the bug number mistyped? Seems unrelated.</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>