<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Can't delete a table in Impress/Draw if cells are selected" href="https://bugs.documentfoundation.org/show_bug.cgi?id=78326#c30">Comment # 30</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Can't delete a table in Impress/Draw if cells are selected" href="https://bugs.documentfoundation.org/show_bug.cgi?id=78326">bug 78326</a> from <a class="email" href="mailto:eyalroz@technion.ac.il" title="Eyal Rozenberg <eyalroz@technion.ac.il>"> Eyal Rozenberg</a> <pre>(In reply to Stepas Toliautas from <a href="show_bug.cgi?id=78326#c28">comment #28</a>) > (In reply to Heiko Tietze from <a href="show_bug.cgi?id=78326#c27">comment #27</a>) > > The user expects operation on the whole object (cut or delete) without > > dependency to any selection state. > > Well, that cannot be true It is empirically true. That is, when a user clicks the frame of a table, or another object, they expect an operation on the entire object. At least, many, and I'd say almost all, users expect this. > otherwise one of the following would be > impossible: a) selecting and cutting/ deleting content of all cells at once, A user expects that clicking-down in some corner cell, then dragging along the diagonal, would eventually select all cells; and a minor expectation is that, at that point, a Delete keypress would clear cenn contents, not the entire table. In other words - users expect a single-click on the frame to do something different than selecting all cells. > or b) selecting and cutting/ deleting the table itself. So there has to be a > difference between table and content selection states. Indeed. But single-click on the frame must effect the former, not the latter.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>