https://bugs.documentfoundation.org/show_bug.cgi?id=142446
--- Comment #24 from clstal.j...@gmail.com --- I came here hoping that I was simply missing this feature in writer, but I find that there's a long history of others needing this functionality too and I'm unclear if it will be included in a planned release or if it is documented and may or may not be added. I agree with j.a.swami, as a user who doesn't use navigator at all, my primary use for collapsing headers is to navigate very long documents, especially those with multiple similar sections (ie 2 high level topics with both having legal/budget/actions/etc as sub-headings). Scrolling in that case is a nightmare, but I don't want to loose the screen real-estate by using navigator since most of what I'm doing is reading and typing. I was, however, surprised at the idea that hidden text would not be included in searches or printed. I think of 'folding' or 'collapsing' as a "view" rather than a functional change. The function is related to formatting (H1, H2, etc), but not printing or search because the text is still there, just out of my current view. If I'm alone in that expectation, perhaps a reminder to the user when printing if you find others have different expectations? I don't see a downside to including all text in search - if the user wants a word count or formatting or search applied to only some of the text, highlighting it and then searching makes more sense to me. If my collapsed/hidden text was not visible and wasn't coming up in search results I would go looking for an existing bug report. If you'd like another example of this feature in action, I also use workflowy because of similar functionality. However, I use that primarily for to-do lists. However, it's a nice example of implemented folding/collapsing functionality. I don't work for or have any affiliation with them, and I don't think I even have a paid account, use any of the new features, or have the app, so this isn't a shill comment, but simply a non-Redmond example of the functionality being discussed. https://workflowy.com/features/ As an N of 1, I wouldn't plan on using 'collapse until level X' functionality at all (other than collapse or expand all). The way I use that feature is to examine and edit sections of the document without tons of scrolling as a user who doesn't use navigator. My interaction is on a heading-by-heading basis by clicking the + or - . I'm not sure that matters, but thought I'd throw that out there as the functionality to collapse and un- collapse by interacting with the headers/not navigator is my highest priority feature request. -- You are receiving this mail because: You are the assignee for the bug.
