Summary: | Custom shortcut for uno:BackgroundColor should set last color not NoFill | ||
---|---|---|---|
Product: | LibreOffice | Reporter: | Robert Lacroix <muxlab> |
Component: | Calc | Assignee: | Not Assigned <libreoffice-bugs> |
Status: | NEW --- | ||
Severity: | normal | CC: | heiko.tietze |
Priority: | medium | ||
Version: | 6.1.5.2 release | ||
Hardware: | x86-64 (AMD64) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
Crash report or crash signature: | Regression By: | ||
Bug Depends on: | |||
Bug Blocks: | 98259 |
Description
Robert Lacroix
2020-12-07 20:08:05 UTC
The command .uno:BackgroundColor is the widget at the formatting toolbar to set the background color. Clicking this widget applies the last used color (or no fill) to the selected cells, clicking the expander opens the listview. It's very purposeful to not toggle: imagine you want to set the background of some non-adjacent cells to the same color. So clearly NAB/WF. Depending on your workflow you might love the cell style feature. OK, I agree and withdraw the request for toggle functionality as a proposed solution. So then how about just fixing the bug, your way? I expect the custom keystoke to apply the last used background colour, as you stated. The keystroke instead only applies "no fill" regardless of the last used background colour. Do you expect the custom keystroke to apply the last used background colour that was set at the time the key was bound to the function, or to apply the last used background colour at keypress time (as I expected)? I confirm that neither behaviour works, i.e. the custom keystroke ALWAYS uses "no fill". This is the bug that I raised, which was not addressed in the response. (In reply to Robert Lacroix from comment #2) > I expect the custom keystroke to apply the last used background colour... Me too :-) Dear Robert Lacroix, 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 |