Created attachment 126596 [details] Screenshot Since LO 5.2 selection colors within template browser as well as within recent documents view changed from light gray / dark gray to light grey / dark blue (see screenshot attached). I'm not sure whether it is intended or a bug. From my point of view selection colors should be reverted to light gray / dark gray.
Confirming also on Version: 5.3.0.0.alpha0+ Build ID: 66fc20335348ec195237c711edca821d8771439c CPU Threads: 2; OS Version: Mac OS X 10.11.6; UI Render: default; Locale: fr-FR (fr.UTF-8); Calc: group
@Jay : do you know if this choice was intended ? (I guess so)
I noticed this as well a few days back. In 5.1, the selected entry was light gray and went dark gray, while now its light gray to dark blue.
This is not a bug, it's a feature. In LO 5.1, the templates view has only three states: unselected(white), selected(dark grey) and hover(light grey). In the new template view, we have four states: unselected(white), selected(dark grey), hover(light grey) and selected + hover (blue). Note that these colour may change depending on system configuration.
(In reply to Akshay Deep from comment #4) > In the new template view, we have four states: unselected(white), > selected(dark grey), hover(light grey) and selected + hover (blue). The colors in the template manager look good but the ones in the start center dont look as good, so please swap the colors of selected and selected + hover (selected to blue and selected + hover to dark grey)
Adding keyword 'bibisectRequest'.
Issue is already present with current master. New four state behavior seems to be only used when selecting "Templates" from Start Center before. Without selecting "Templates" from Start Center behavior is as known from the past.
1339374c9eee9abf83a165cda082ceef3e504b63 is the first bad commit commit 1339374c9eee9abf83a165cda082ceef3e504b63 Author: Jenkins Build User <tdf@pollux.tdf> Date: Tue Sep 27 13:52:14 2016 +0200 source 934908168ebdb4a021e18e6bea57accc21d5ad86 source 934908168ebdb4a021e18e6bea57accc21d5ad86 :040000 040000 1c49c419464868e001c42e456e4622976056a2cb 576de6db379dc5960cc974e6a323da6a94de69a5 M instdir
# bad: [1bfd8dda84f0dd2c5662b64f382637d75b8bf227] source 6238f71ddbdc766e733b1c808a4fa7d66f7bde87 # good: [33e60eae04c889baf52713a73dc9944015408914] source 5b168b3fa568e48e795234dc5fa454bf24c9805e git bisect start '1bfd8dda84f0dd2c5662b64f382637d75b8bf227' 'oldest' # bad: [964789dfd0674f0447da363a8c52114097796fa3] source e473e0e1b9bc354d53908cb0ca84db06c3051fe2 git bisect bad 964789dfd0674f0447da363a8c52114097796fa3 # bad: [e076e507d65a9ac4e63569e22b7384a0eb67c5a0] source 8550366138d576123b9e66a1a7915a04026d79cd git bisect bad e076e507d65a9ac4e63569e22b7384a0eb67c5a0 # bad: [720bbf801075947ba622f09ee203a45582abbc37] source 6b3eb4788f63602c0a446ad8f56539d3b65bb302 git bisect bad 720bbf801075947ba622f09ee203a45582abbc37 # good: [b3cece56b78e9650587bb1d2cf67ea09a6386e56] source 2a11499583cfc8c65e2fa99fbcdfdd7b94e966c1 git bisect good b3cece56b78e9650587bb1d2cf67ea09a6386e56 # bad: [aff42b2b4d7417bf87e012f814f47496b18aad29] source 99226f343e4ad9ebcbb4e31c17d3fb706153e18b git bisect bad aff42b2b4d7417bf87e012f814f47496b18aad29 # bad: [791dd96fd23f4152197b00ea470d5dac13868c6c] source a7415828b86a02216ffed44a4fa5b785f17d657c git bisect bad 791dd96fd23f4152197b00ea470d5dac13868c6c # bad: [819d07d26f254d871438c19c52daa3f101fc950d] source d106ffc5f1c611657e7ccd96ac9dab70cc7ebe53 git bisect bad 819d07d26f254d871438c19c52daa3f101fc950d # bad: [a138f67ed7ef4f0a9280e68c423222c2752d48b4] source 45a6fdad8101e4ba552ca4d4532d0b03b79dd15a git bisect bad a138f67ed7ef4f0a9280e68c423222c2752d48b4 # good: [9c77eee0c75eb77571587b988b6c101714cd7fd7] source 8f6ce60fdb9a8a583f3a925ef345265cee299b89 git bisect good 9c77eee0c75eb77571587b988b6c101714cd7fd7 # good: [6ac5f1472e47426b6911c4cf766d8e1c14b9e4ac] source d8df3ed9dfef931d5384a18f3ac3b1f49ee3200c git bisect good 6ac5f1472e47426b6911c4cf766d8e1c14b9e4ac # good: [2adf7ecbee036767339ad1ef1b2bb360d3583803] source b5ad72bbfca85946e352b56d9d2ee5eb71cd2132 git bisect good 2adf7ecbee036767339ad1ef1b2bb360d3583803 # good: [cfa971662ead21a290aac472f4cc04b37ff3ec56] source 15436c009e756dd4c94046f9849ad5a186454af8 git bisect good cfa971662ead21a290aac472f4cc04b37ff3ec56 # bad: [1339374c9eee9abf83a165cda082ceef3e504b63] source 934908168ebdb4a021e18e6bea57accc21d5ad86 git bisect bad 1339374c9eee9abf83a165cda082ceef3e504b63 # first bad commit: [1339374c9eee9abf83a165cda082ceef3e504b63] source 934908168ebdb4a021e18e6bea57accc21d5ad86
With this commit, selected + hover is blue, before that, dark grey
bisected keyword is missing here... Regression introduced by: author Akshay Deep <akshaydeepiitr@gmail.com> 2016-06-07 10:57:25 (GMT) committer Samuel Mehrbrodt <Samuel.Mehrbrodt@cib.de> 2016-06-07 12:58:17 (GMT) commit 934908168ebdb4a021e18e6bea57accc21d5ad86 (patch) tree 3ab87af564a6f62c55282cc005d09cf25873b6e0 parent 15436c009e756dd4c94046f9849ad5a186454af8 (diff) Missing selected + hover state in Template Manager Adding Cc: to Akshay Deep
** 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
Issue still exists in current revision from master (LO 6.3).
Can we resolve this issue? Don't see a way to select as single click opens the object.
I would prefer an easier handling: (1) Single click to open recent document or template (2) Moving around with tab / shift tab to select a recent document or template by means of keyboard, pressing return to open selected recent document or template Don't know what use case has to be covered by a three state value. In any case: OS specific colors for selections should be used.
(In reply to Thorsten Wagner from comment #15) > (2) Moving around with tab / shift tab to select a recent document or > template by means of keyboard, pressing return to open selected recent > document or template That brought me to the answer: use the keyboard to multi-select - and hoover will add to the selection. Still blue, as defined in the options.
What is the use case for a multi-select within Startcenter?
(In reply to Thorsten Wagner from comment #17) > What is the use case for a multi-select within Startcenter? No idea. Neither for the template manager which share the same code.
Dear Thorsten Wagner, 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
With gtk3 VCL plugin, reproduced in 7.0.6.2, but not anymore in: Version: 7.1.0.3 / LibreOffice Community Build ID: f6099ecf3d29644b5008cc8f48f42f4a40986e4c CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded It now uses the system's highlight colour. On macOS however, I can still reproduce in 7.6.4 but on master it uses a nicer light blue that matches the OS highlight colour. Note that there is now no difference in colour between selected and selected + hover. So to me this is "works for me". Heiko might have more details on recent changes regarding the use of system's highlight colour in various places. I suspect the 24.2 change is related to bug 158084. (In reply to Thorsten Wagner from comment #17) > What is the use case for a multi-select within Startcenter? This issue has been resolved with bug 158404.
(In reply to Stéphane Guillou (stragu) from comment #20) > related to bug 158084. Before this patch we used some color for hover and another for highlight, both available via expert option, which has now changed to system colors (highlight and active as defined by the OS/DE).