Date: prev next · Thread: first prev next last
January 2020 Archives by date, by thread · List index


https://bugs.documentfoundation.org/show_bug.cgi?id=129471

V Stuart Foote <vstuart.foote@utsa.edu> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |vstuart.foote@utsa.edu

--- Comment #5 from V Stuart Foote <vstuart.foote@utsa.edu> ---
+1 for keeping the navigate by with the Find bar, but hiding it by default (for
Eve users to set enabled with toolbar Visible button).

As to sorting, IIUC the listbox for .uno:NavElement was taken from sequence in
the the Navigator's Navigation floating toolbox.

Caolán has removed the toolbox dialog (against bug 130004) [1] but keeping the
old sequence, and Jim has a patch up for review [2] to now use the same
.uno:NavElement control replacing the toolbox on the Sidebar, but still with
the old sequence.

Believe we are free to reorder the listbox sequence.

But for UX we would need to consider any change of sequence affects both the
Find bar and the Navigator. 

What is the best order then? An alpha sort would not necessarily be best. Needs
functional grouping (add separators maybe).

=-ref-=

[1] https://gerrit.libreoffice.org/c/core/+/86874
[2] https://gerrit.libreoffice.org/c/core/+/87005

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.