<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Smaller default font name list" href="https://bugs.documentfoundation.org/show_bug.cgi?id=91130#c26">Comment # 26</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Smaller default font name list" href="https://bugs.documentfoundation.org/show_bug.cgi?id=91130">bug 91130</a> from <a class="email" href="mailto:tietze.heiko@gmail.com" title="Heiko Tietze <tietze.heiko@gmail.com>"> Heiko Tietze</a> <pre>(In reply to Ole Tange from <a href="show_bug.cgi?id=91130#c25">comment #25</a>) > > What I refuse (and other people I talked to as well) is the multi-column output. > Can you elaborate on why? You focus on the presentation of the list content while dropdowns and list views usually are there to select an item. When those lists grow the typical approach for quicker selection is a filter on typing and proper sorting. Your proposal is not a lightweight standard control anymore and has accessibility issues. In a one-dimensional list the navigation is done per cursor up/down while two dimensions multiply the effort (plus all the trouble around impaired users that have to relay on screen readers). And mentioned before I doubt that scrolling works nicely as your columns are filled unequally. > I can justify why I prefer the multi-column output: IMHO the goal is to > quickly identify and select one item. If you read interface styleguides you will not find the identification aspect being relevant for lists. Your idea is nice for the overview (I would focus on this part ignoring column types), additional to the selection. And you could realize it yourself as an extension. How about that?</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>