https://bugs.freedesktop.org/show_bug.cgi?id=69157
--- Comment #11 from tmacalp <tmac...@gmail.com> --- (In reply to comment #10) > > However, when the user sees that the picture moves, in stead of the frame, > it will be natrural behaviour to put the mouse on the frame border... so I > consider this not a sever problem... > (just IMO of course) While this bug might have an easy work around, it's still quite annoying and something I still hope to be fixed. It is also an obvious regression that affects commonly used behavior, which typically warrants an elevated priority. By the way, what is the intended behavior for selecting objects contained in a selected frame in Writer? It appears that bug 55430 implemented the ability to select an object in the foreground of another selected object in Draw. Is the current similar behavior in Writer a side effect of that patch? For instance, If I have a pictures, frames, or draw objects anchored to and within a selected framed, I can now single click these items to select them. This ability came with 4.1.0. I will say that this is functionality I've been wanting for a while, especially for working with large full-page frames. Of course, this feature only applies to selecting interior objects (frames, draw objects, pictures). Would a user also expect a single click on a section of text to deselect the frame and take you into text edit mode as well? What about clicking on a table border or blank area within a frame? (In reply to comment #6) > > Note: This strange behavior seems to be some other sort of moving. the mouse > cursor has a rectangle attached to it, which is a hind of moving that allows > to move the item to other windows. In Impress, it only occcurs after waiting > some time. You're right! This observation is quite interesting. The original steps to reproduce immediately move the image with the long-click type move icon/behavior. My guess is the current buggy behavior is from only addressing the a normal move case and the other long-click "move-between-window" move type was not addressed. It's almost as if this unexpected move attempt short-circuits the the standard long-click delay. -- You are receiving this mail because: You are the assignee for the bug.
_______________________________________________ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
