A blue rectangle is being draw over my drawing when using the "Align" tool to change the table's position. The rectangle's original use seems to be to highlight one of the table but it stays drawn at the table's original location until I close my drawing. Steps to reproduce: 1. Add two tables to the drawing 2. Move one of the table so that the two are no longer vertically aligned. 3. Select the two tables. 4. Use the "Align" tool to left-align the two tables. 5. The table that was moved during the action will have a blue box draw over it. 6. Click in the non-blue table to select it 7. The other table will still be blue. 8. Select and Move the blue table 9. The blue rectangle will stay at the table's original location. It is now impossible to make the blue box disappear unless you save and close the document and then reopen it. Note that if you where to select the blue table at step 6 instead, the blue box would disappear.
You can also reproduce this by selecting the two tables and moving them. After they have been moved, one of the two tables will be blue (if not, move them again). Once the blue table is there, select the non-blue one then try to move the blue one. The blue rectangle will stay at the table's original location.
No problem at all here. Two tables, select both, align > left: works like a charm. Version: 5.1.3.2 Build ID: 5.1.3.2 Arch Linux build-1 CPU Threads: 8; OS Version: Linux 4.5; UI Render: default; Locale: de-DE (de_DE.UTF8)
Reproduced, but indeed it's only related to moving, and not to alignment. Steps: Have a table selected (create it or select it). Move table. Undo. => Blue rectangle denoting selection doesn't move back (new selection makes it disappear). Tested and affected: LO 4.1.0.4, 5.1.3.2, master in Windows 7. 5.1.3.2 in Linux. 4.1.0.4 was the first release that had blue rectangle upon selection. As it's a visual bug with negligible impact, reducing severity to minor.
(In reply to Aron Budea from comment #3) > Have a table selected (create it or select it). Move table. Undo. > => Blue rectangle denoting selection doesn't move back (new selection makes > it disappear). Confirmed (Windows, 5.2). Renamed the issue and set it for evaluation as easyhack in case a simple call to refresh is needed.
NEEDINFO for the code pointers.
Heiko, NEEDINFO [1] is for the reporter to provide more information, and I don't think they can help with code pointers. [1] https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO
(In reply to Aron Budea from comment #6) > Heiko, NEEDINFO [1] is for the reporter to provide more information, and I > don't think they can help with code pointers. ESC decision. Bug 48015, comment 12 and following for more infos.
(In reply to Heiko Tietze from comment #7) > ESC decision. Bug 48015, comment 12 and following for more infos. I see, that's good to know, thanks for the reply.
Removing keyword 'needsDevEval' as this bug is an easyHack
not an easyhack
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (5.4.1 or 5.3.6 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170929
Dear Eric B., To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Dear Eric B., To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug