<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_UNCONFIRMED " title="UNCONFIRMED - Separate outline browsing and heading browsing in Navigator" href="https://bugs.documentfoundation.org/show_bug.cgi?id=141456#c3">Comment # 3</a> on <a class="bz_bug_link bz_status_UNCONFIRMED " title="UNCONFIRMED - Separate outline browsing and heading browsing in Navigator" href="https://bugs.documentfoundation.org/show_bug.cgi?id=141456">bug 141456</a> from <a class="email" href="mailto:mikekaganski@hotmail.com" title="Mike Kaganski <mikekaganski@hotmail.com>"> Mike Kaganski</a> <pre>(In reply to Eyal Rozenberg from <a href="show_bug.cgi?id=141456#c2">comment #2</a>) > (In reply to Mike Kaganski from <a href="show_bug.cgi?id=141456#c1">comment #1</a>) > > Styles with names starting with "Heading" are not any special, > > Well, they're mentioned specifically in the Navigator. No. No styles are named in Navigator, only a term "headings", which is related to outline level (by LibreOffice definition); and if somewhere there's a mention of "navigator shows Heading N styles", that is a bug that needs fixing. The "co-incidence" of the style naming only reflects "these styles were created to be used like this, and have all required properties by default". We must *not* hardcode special processing of any styles, unless absolutely unavoidable, ever. > > Only outline level (assignable to any paragraph, > > or to any paragraph style) makes a paragraph a heading; > > Outline level is not "Heading level". Something participating in the outline > does not have to be a heading and vice-versa. Outline level *is* heading level in LibreOffice. Period. > > Implementing this proposal would decrease flexibility (so users would always see these styles in navigator, even if they don't use these as headings). > > 1. They would only see these styles in Navigator if they chose to look at > Headings. Just like now they "always see" frames, or bookmarks, or comments. But they would not be able to avoid the special-casing; and they would be confused by the two obviously different lists, that by default would be identical, and if used chooses to use a different set of paragraphs for outline, they would represent a strange thing (Heading list empty, or lists a different set, compared to user expectations). > 2. No flexibility decrease, since users would have the same functionality > they have now under "Outline". My suggestion only _adds_ functionality. No, it only adds confusion: what is a *practical* use case that this solves, and how could that compare to the inevitable confusion on most users mentioned above?</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>