https://bugs.documentfoundation.org/show_bug.cgi?id=94287
tmacalp <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.documentfounda | |tion.org/show_bug.cgi?id=34 | |585 --- Comment #8 from tmacalp <[email protected]> --- (In reply to Armin Le Grand from comment #6) > 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. I actually use frames within frames quite often. For instance, you would need a frame within a frame any time you have a captioned picture in a frame. Frames are vital for handling complex page layouts. I agree with you that the current none-filled frame behavior is confusing and needs to die. It's obviously not a decision to be taken lightly, but we will need to bite the bullet at some point. A decade ago this behavior was already referenced as a "historical design flaw." As mentioned in my original post, the primary report for that behavior is bug 34585. Since it's somewhat related, I'll add it as a see-also. -- 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
