https://bugs.documentfoundation.org/show_bug.cgi?id=149271
--- Comment #3 from Eyal Rozenberg <[email protected]> --- (In reply to Mike Kaganski from comment #2) > I don't see what aggregation of several styles of the same category could > mean for a style category like paragraph, where styles by definition define > every single property Well, not if you consider inheritance. > (either directly, or by inheritance). Ah, but that's the point. If we have styles A, B, C with B and C inheriting A, then applying B and C means applying both the changes B makes to A and the changes C makes to A. Naturally there's the question of conflicts. This can be settled either by order of application (i.e. search orders C,B,A or B,C,A with the A being implicit), or arbitrarily, i.e. the app doesn't guarantee which of B and C's changes would be used, and it's the user's problem. Since all styles inherit from the Default Style of their kind, we don't have the problem of multiple inheritance-roots. For a concrete example, think of Default Page Style, RTL page, and a DecorativeFrame style. Each of the child styles only defines what its name suggests. The composition would be "RTL, DecorativeFrame" (or the other way around, doesn't matter). -- You are receiving this mail because: You are the assignee for the bug.
