<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Add ability to "fix" badly imported floating tables with a single click" href="https://bugs.documentfoundation.org/show_bug.cgi?id=112704#c3">Comment # 3</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Add ability to "fix" badly imported floating tables with a single click" href="https://bugs.documentfoundation.org/show_bug.cgi?id=112704">bug 112704</a> from <a class="email" href="mailto:baron@caesar.elte.hu" title="Aron Budea <baron@caesar.elte.hu>"> Aron Budea</a> <pre>Oops, forgot to reply, my bad. (In reply to Heiko Tietze from <a href="show_bug.cgi?id=112704#c2">comment #2</a>) > What I don't understand is why we should find a mechanism for broken content > when the roundtrip could be fixed so that nothing breaks. Fixing the roundtrip, eg. adding support to floating tables would be quite some work (I don't have an estimation, though). The tuning of heuristics are for relatively specific cases, and a new one can pop up anyime, eg. <a class="bz_bug_link bz_status_NEW " title="NEW - DOCX with floating table having 100% width incorrectly imported" href="show_bug.cgi?id=114217">bug 114217</a> surfaced just now. > Second idea, if there is some good reason for such a feature: In the table > properties dialog we have an option "Allow table to split across pages and > columns". Users may expect auto-repair by unchecking this option, which is > not happening because of the frame I guess. But can't we modify this > function and remove the frame? Perhaps after confirmation. I'm a bit afraid that adding extra "hidden" functionality to that checkbox is something that might elude users, I'd prefer it as a separate frame-removing button (or maybe have both). I guess that'd also have more impact on the UI, which might be undesirable...</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>