Created attachment 132072 [details] Screenshot Open two Writer windows, have Properties sidebar enabled and put them side-by-side. Note how Highlight Color selector is missing and Set Character Spacing is not enabled in the inactive window, and reappers when it's active. Reproduced in 5.3.1.2 and 4.3.0.4 / Windows 7. Not reproduced in 4.2.0.4. => regression
Some more observation: - In Writer, if the cursor is in a text box or a table, there will be changes in the paragraph sidebar panel. (This one can be reproduced with 4.2.0.4 too.) - In Calc, if the cursor is in a text box, the Style sidebar panel will appear. - In Writer with notebookbar enabled, if the cursor is in a table, the notebookbar will turn blank. All this stops after commenting the ContextChangeBroadcaster::Deactivate method [1]. Obviously the various sidebar/notebookbar panels were not prepared to handle this vcl::EnumContext::Context::Default notification. IMHO the usefulness of considering a "window lose focus" event as an application context change is questionable, as well as the vcl::EnumContext::Context::Default purpose in a whole. [1] http://opengrok.libreoffice.org/xref/core/sfx2/source/sidebar/ContextChangeBroadcaster.cxx#54
Bibisected the first issue down to the following commit using repo bibisect-43max. https://cgit.freedesktop.org/libreoffice/core/commit/?id=bc46764f12947cbe8d46e03450f181d449c020f4 commit d9b101f0670ac0cd1ec41c51ad4d6a5d71dd0271 Author: Matthew Francis <mjay.francis@gmail.com> Date: Thu May 28 18:46:30 2015 +0800 source-hash-bc46764f12947cbe8d46e03450f181d449c020f4 commit bc46764f12947cbe8d46e03450f181d449c020f4 Author: Maxim Monastirsky <momonasmon@gmail.com> AuthorDate: Mon Jan 27 13:58:41 2014 +0200 Commit: Caolán McNamara <caolanm@redhat.com> CommitDate: Thu Jan 30 11:56:01 2014 +0000 Sidebar Text panel cleanup Change-Id: I6cbf5a9e5ad9d61df2abbcc835ba60d45768deeb Reviewed-on: https://gerrit.libreoffice.org/7687 Reviewed-by: Caolán McNamara <caolanm@redhat.com> Tested-by: Caolán McNamara <caolanm@redhat.com>
** 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 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
Adding Cc: to Maxim Monastirsky
*** Bug 117251 has been marked as a duplicate of this bug. ***
Dear Aron Budea, 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
Still in LO 7.1.0.0.alpha0+ (abea0d6647c7f1f7e76c73c26cb80e6a67dc5111).
Dear Aron Budea, 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