<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_UNCONFIRMED " title="UNCONFIRMED - new feature gutter-margin in LO7.2 produces unnecessary incompatibility with LO7.1" href="https://bugs.documentfoundation.org/show_bug.cgi?id=141345#c3">Comment # 3</a> on <a class="bz_bug_link bz_status_UNCONFIRMED " title="UNCONFIRMED - new feature gutter-margin in LO7.2 produces unnecessary incompatibility with LO7.1" href="https://bugs.documentfoundation.org/show_bug.cgi?id=141345">bug 141345</a> from <a class="email" href="mailto:vmiklos@collabora.com" title="Miklos Vajna <vmiklos@collabora.com>"> Miklos Vajna</a> <pre>(In reply to Xisco Faulí from <a href="show_bug.cgi?id=141345#c2">comment #2</a>) > Created <a href="https://bugs.documentfoundation.org/attachment.cgi?id=170856" name="attach_170856" title="LibreOffice 7.1 vs LibreOffice 7.2">attachment 170856</a> <a href="https://bugs.documentfoundation.org/attachment.cgi?id=170856&action=edit" title="LibreOffice 7.1 vs LibreOffice 7.2">[details]</a> > LibreOffice 7.1 vs LibreOffice 7.2 Sure, it's expected that a new feature in 7.2 doesn't work in 7.1 :-) That's the case for any new feature. A close example is e.g. contextual spacing, obviously if you use that new feature, then old versions won't be able to render it. We're backwards compatible, not forward-compatible. The bugreport is about if we can introduce workarounds to have a markup that looks better on 7.1, without modifying 7.1. I understand the benefit of that, although doesn't like to introduce hacks for something new. I'll think about how to implement this, this would mean that loext:margin-gutter has to be taken into account when importing fo:margin-top, fo:margin-left and fo:margin-right. Sounds like a huge amount of work, but perhaps later I or somebody else will came up with a creative idea how to do this.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>