https://bugs.documentfoundation.org/show_bug.cgi?id=94287
--- Comment #6 from Armin Le Grand <[email protected]> --- Probably has to do with that commit - this was the deep change to allow for any standard-FillStyle combination for Writer Frames/Pages/... This was not only for transparency, but for none/color/gradient/hatch/graphic fill and shadow. Someone has to decide if this is an error or not, as already claimed in the related notes. I remember that I was astonished myself about 'None' leading to inherit from parent when implementing. As it seems I missed at that time that 'inherit' is only for non-overlapping parts of child and parent. Or the other way round: Do not inherit in overlappinmg parts (equivalent with not painting child in overlapping parts?). All this is confusing and from my POV not what a user expects. When the user sets a child frame to fill==none, it just should not be filled. Everything else is unintuitive for me. Instead of adding work for this case (frames in frames, hopefully not used often) I pled for using 'None' as none, same as transparency==100%, no fill. No inherit from parent frame. As tmacalp mentions, this will break compatibility. -- You are receiving this mail because: You are the assignee for the bug.
_______________________________________________ Libreoffice-bugs mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
