<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#c8">Comment # 8</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:mikekaganski@hotmail.com" title="Mike Kaganski <mikekaganski@hotmail.com>"> Mike Kaganski</a> <pre>I suppose that using an infobar is a bad idea. Table in a frame is not something "wrong", such that most possibly requires fixing. Yes, the cases that need the fixing are numerous enough that we would better have the feature to convert tables-in-frames to ordinary tables (until we have a proper floating tables support, which will take quite some time); but popping up an infobar on entry to such a table will bring content jumping (similar to one that we had when table and lists context-sensitive toolbars were attached to top, which was intrusive enough to reconsider their placement to the bottom of window). So, this would make the life of those who work with such floating objects routinely more difficult. I suppose that the functionality is close enough to "Convert text to table/table to text" in its spirit; it deserves a place in table menu, and possibly a button on a toolbar, where it might hide, of course, but it's not a big problem.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>