https://bugs.documentfoundation.org/show_bug.cgi?id=147004
--- Comment #22 from Mike Kaganski <[email protected]> --- TL;DR (In reply to Heiko Tietze from comment #18) > Thought this was about empty fields (fine for me = NAB) not any heading > greater or equal the level (which is totally unexpected and I see no reason > to do so). You do some modifications for the understanding now, and that's > great. I wouldn't wait for volunteers to pick up the implementation error. I might misinterpret this sentence; let me first tell how I understood it, and then argue with that my understanding of the phrase. I understood it as "I see no reason for a user to set the field's level to a value greater than the existing outline level; thus, it's a user error, no change is needed, and just a documentation improvement is necessary". There *is* a reason to have this "level value greater than outline level". It is common that books have, say, chapter (let it be layout level 1) name shown on the left header, and subchapter (section; layout level 2) on the right header. In this case, it is possible that a chapter (level 1) is already started, but its subchapters (sections, level 2) has not yet (it's some introductory text). In this case, having the chapter name on the right-hand page may *or may not* be desirable. So having a way to fix the field to only show something when there is the required level is really a good thing, but at the same time, the current behavior is not a defect. -- You are receiving this mail because: You are the assignee for the bug.
