<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - FILEOPEN DOCX TAB_OVER_MARGIN not needed for compatibiltymode >= 15" href="https://bugs.documentfoundation.org/show_bug.cgi?id=142404#c24">Comment # 24</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - FILEOPEN DOCX TAB_OVER_MARGIN not needed for compatibiltymode >= 15" href="https://bugs.documentfoundation.org/show_bug.cgi?id=142404">bug 142404</a> from <a class="email" href="mailto:jluth@mail.com" title="Justin L <jluth@mail.com>"> Justin L</a> <pre>I'm tempted to mark this as fixed, even though <a href="show_bug.cgi?id=142404#c0">comment 0</a>'s 40787_TabsAtEndOfParagraphC15.docx isn't yet identical to Word 2016. That's because Word does REALLY STRANGE THINGS. If the tab is connected directly to a word, the word is pulled down, and then the tab follows - usually again on another line. When - as in this case - the tab follows some whitespace, then only the tab starts a new line, and it does NOT pull down any of the whitespace. So there is still a difference, since I don't have the first tabstop always start on a new line. But that doesn't seem logical to do that, and there seem to be some bugs in MS implementation, so we probably shouldn't try TOO hard to exactly match what we see in Word.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>