https://bugs.documentfoundation.org/show_bug.cgi?id=143907
Eek! A Bug. Kill it! <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution|--- |NOTABUG --- Comment #14 from Eek! A Bug. Kill it! <[email protected]> --- (In reply to Justin L from comment #13) > (In reply to Eek! A Bug. Kill it! from comment #12) > > I do not understand how you can state that there is no problem because it > > only happens on one level - especially when you go on to point out that this > > same thing happened in the past, but on a different level. > Make sure you read the earlier responses carefully. I never said it wasn't a > problem because it only happens on one level. > > Yes, in the past the style set a specific zero margin on ALL heading styles, > but that was fixed in 5.2 (including for level 3). > > That bug/fix is completely disconnected from the reason why level 3 is > causing you trouble though. I explained why earlier, and you can unzip your > document and look at styles.xml and see that only Heading 3 has a left > margin specified (as zero). Based on the instructions in the style > definition, LO is doing exactly what it is told to do, and that is why there > is no problem. > > > The same thing happens on any document I create from scratch > Please do make this new example from scratch and submit it. I would actually > be surprised if you can do it. Make sure you document all the steps so that > others can reproduce it too. > > > The process you outlined may work, but it is too involved for the > > average user to implement, and it should not be necessary in any case. > The average user will never run into this situation. This only happens when > a style is changed to give it a non-default value. (And this is a perfectly > legitimate operation that some users might want to do intentionally. > Everything here is consistently following the rules of inheritance priority.) > > My process is not actually complicated. > -the user somehow specifies a setting in a style, but now wants to clear > that direct setting and inherit it from the parent style instead. > -the user presses the Reset to Parent button on the relevant tab (previous > just labelled as "Standard" I expect). > > Powerful software by definition allows complicated situations. Justin, it seems that I owe you a sincere apology. I was struggling to learn the whole styles method of creating documents and must have somehow changed that level 3 left outline list margin setting inadvertently because I have no recollection of having done so (it was after all a fairly short test document that I created specifically to follow along with a LO Writer Styles video tutorial). I was aware from my reading of the manual that direct formatting takes precedence, which makes sense, but I did not think I had changed any settings directly. I made use of the Style Inspector and noticed what you did, but I could not find a way to manually change the errant margin setting, and since everything in the Bullets & Numbering dialog looked correct (except as noted), I presumed there was indeed a bug. You were also correct in that the problem did NOT exhibit itself in a new document, which I am absolutely certain I tried before writing this bug report to verify my bug assumption, but alas a new document today works fine. Not sure why, but obviously it’s either something I did (if you make a mistake once, you are apt to make the same mistake again moments later due to muscle memory) or it’s this touchy Asus keyboard once again having a mind of it’s own. -- You are receiving this mail because: You are the assignee for the bug.
