<html>
<head>
<base href="https://bugs.documentfoundation.org/">
</head>
<body><span class="vcard"><a class="email" href="mailto:glogow@fbihome.de" title="Jan-Marek Glogowski <glogow@fbihome.de>"> <span class="fn">Jan-Marek Glogowski</span></a>
</span> changed
<a class="bz_bug_link
bz_status_NEW "
title="NEW - Elements pane: Items not reachable without mouse"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=65587">bug 65587</a>
<br>
<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>What</th>
<th>Removed</th>
<th>Added</th>
</tr>
<tr>
<td style="text-align:right;">Keywords</td>
<td>
</td>
<td>needsUXEval
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Elements pane: Items not reachable without mouse"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=65587#c17">Comment # 17</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Elements pane: Items not reachable without mouse"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=65587">bug 65587</a>
from <span class="vcard"><a class="email" href="mailto:glogow@fbihome.de" title="Jan-Marek Glogowski <glogow@fbihome.de>"> <span class="fn">Jan-Marek Glogowski</span></a>
</span></b>
<pre>FYI: this just implements the KeyInput handling. Strictly taken, the bug is
fixed.
What is still missing is the Accessibility integration, which is a mess in LO.
Originally these elements were handled by a Toolbox, represented as various
buttons. I generally plan to go the same way. But I'm not yet sure if I should
abstract the Toolbox, so it's accessibility implementation will fit the new
control, or write a completely new one accessibility integration. Then there is
the additional scrollbar.
The control itself is a mix between a list box (scrollable list of items) and a
toolbox (list of buttons). It doesn't really matter that the visual
representation is more of the grid, because the navigation is currently handled
as a list of items, as this is the internal representation.
An other question: should the accessibility always list all buttons,
independent of the ScrollBar (which means it lists buttons currently not
visible)? My guess is the various list themselves will never be long, but the
ScrollBar is definitely needed.
And while at it: should the navigation work as a cycle, AKA the next item after
the last item will be the first item again?
The current implementation generally works, but I consider it a working PoC and
would like to get some comments.
BTW: navigation implementation as a real grid is currently out of scope! If you
want that, please file an additional bug report and discuss it there.</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>