It would be great that when you prompt the command "highlight" over a text already highlighted with the same colour, the highlighting would be deleted. This would make it much easier for users reading long files in fullscreen mode and highlighting with a shortcut, and would avoid setting the "No fill" option on and off after and before de-highlighting a passage.
marked as enhancement request
For two reasons I'd have thought the fact that it doesn't do this already would actually be a bug and not an enhancement request. 1) The whole point of the highlighting feature is to be able to easily highlight and unhighlight sections of text, and currently there is no way to unhighlight text at all without resetting your configured highlight colour to No Fill, which is obviously extremely unhelpful as it obliges you to have to manually reapply your preferred highlight colour every single time you unhighlight something. 2) Clicking Highlight again to unhighlight is the way all other word processors support this feature and there is no reason why Libre Office should implement this any differently. Recategorized as normal severity Bug.
** 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 (4.4.1 or later) 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 your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-04-01
The bug is still present in LibreOffice 4.4.2.2 run in Lubuntu 14.04.
** 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.0.5 or 5.1.2 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 your help! -- The LibreOffice QA Team This NEW Message was generated on: 2016-04-16
The bug is still present in LibreOffice 5 run in Xubuntu 16.04.
** 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-20170901
Still present on 5.1.6.2 running on Kubuntu 16.04.
So you are talking about a character style and not direct formatting? But anyway, I object the idea to temporarily unapply properties and suggest you format the documents in a way that it can be read easily.
I'm not sure you are understanding the issue. What info do you need? Would screenshots help?
We want highlighting to behave like italics or bold. If you press Ctrl+I in a text in italics, it turns back to normal. Why cant a text highlighted with, say, Ctrl+H can't behave in the same way?
(In reply to Pablo San Martín from comment #11) > We want highlighting to behave like italics or bold. Then it's a WONTFIX. See bug 108751 comment 19. In a nutshell, by making the color functions a toggle buttons we loose the ability to apply a color to many objects. You can use a character style with highlighting attributes and another with no fill, and switch quickly with find & replace. Ctrl+M is another way to quickly get rid of the highlighting if you work with direct formatting.
(In reply to Heiko Tietze from comment #12) > Then it's a WONTFIX. See bug 108751 comment 19. I'm not asking to "update the font color and highlight color icons based on current focus in the text". But rather: "Only when and if the current highlight colour and the existing highlighting is the same, when running the command "highlight" it should "de-highlight"." Is that also a WONTFIX?
Sorry, it wasn't so clear: "When and if the current highlight colour is the same as that of the selected (and already highlighted) passage, running the command "highlight" it should "de-highlight" it."
Ctrl+M works, thanks! But it's really not that intuitive, as italics and bold are.
(In reply to Pablo San Martín from comment #14) > Sorry, it wasn't so clear: "When and if the current highlight colour is the > same as that of the selected (and already highlighted) passage, running the > command "highlight" it should "de-highlight" it." Yes, that makes sense. Adjusted the summary accordingly.
Set back to enhancement as it worked till now as intended by the devs. I like and support the idea of de-highlithing the selected area/text if it's the same as the last applied color (which is shown as color in the button). If a part of the selection is not highlighted in this color, clicking the button should highlight it as it does now. This would simplify the workflow for many users. Ctrl+M is not intuitive for most users as they don't know the difference between direct (hard) and style (soft) formatting. Hope that not too many users are confused/disturbed with the behavior change.
SvxColorToolBoxControl is defined in include/svx/tbcontrl.hxx (with a short README) and svx/source/tbxctrls/tbcontrl.cxx
Just for information: MSO 2013 behaves as it is desired in this bug report. Clicking twice at the text highlight color button adds (first click) and removes (second click) the color. But this effect doesn't exist for the font color.
Daniel committed a patch related to this issue. It has been pushed to "master": http://cgit.freedesktop.org/libreoffice/core/commit/?id=bdd7abf56676732f8ce4fd04bea5c72758f1ec3b tdf#63438 Toggle highlight color to no fill if the same value is active It will be available in 6.1.0. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Verified with Version: 6.1.0.0.alpha0+ (x64) Build ID: 8e0eb015e74775b9bf02326ffd7b67e83ad6c60d CPU threads: 8; OS: Windows 10.0; UI render: GL; TinderBox: Win-x86_64@42, Branch:master, Time: 2018-04-03_03:53:38 Locale: de-AT (de_AT); Calc: CL Thanks for the patch, Daniel!
*** Bug 81187 has been marked as a duplicate of this bug. ***