Created attachment 86126 [details] Test file for reproducing the bug Issue in short: in some documents I am unable to remove underlining for hyperlinks and change font color without extra steps to avoid the bug. Steps to reproduce: 1. Open the attached file. 2. Select "Gentoo" word and try to remove underlining - WORKS. 3. Change color to black - DOES NOT WORK. Instead of making the word black, it makes it blue and underlined again. 4. Make the same text italic - now it works as expected. 5. Hit Ctrl+I again and you can see that it is only now what I was supposed to get in step 3.
Reproduced with LibO 4.1.2.3 on Win7 Deals with direct formatting : - select the whole line, Ctrl-m to remove direct styles : after that, it works - Writer seems confused by the multiple formats applied to the word "Gentoo" : the format of the underlying paragraph component, the character formats attached to the status of "hyperlink entry" and the formats (color, underline, etc) that the user try to apply to the word. Bug.
Shouldn't this be marked as confirmed by now?
OpenOffice.org also has this bug: https://issues.apache.org/ooo/show_bug.cgi?id=123220
(This is an automated message.) LibreOffice development currently prioritizes bugs with the so called MAB (most annoying bugs) -- as this bug has not run through that process (including writing a short rationale for this bug being a candidate and other who are watching the tracker bug silently approving that rationale etc.) its priority is set to high. Note this is effectively no change in the urgency assigned to this bug, as we are currently not making a difference between high and highest and severity is untouched. You can find out more about MABs and how the process works by contacting libreoffice qa on irc: http://webchat.freenode.net/?channels=libreoffice-qa The QA wiki page also gives you hints on how to get in contact with the team (if IRC fails you, your next best choice is the mailing list): https://wiki.documentfoundation.org/QA
** 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.2 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-05-02
Still present on version 4.4.2.2 on ArchLinux
Still (annoyingly) present in 5.1.1.3. (Much thanks to Ernestas for reporting and for showing a workaround.) For most people who likely wouldn't even think there's a workaround, it's a major accessibility issue when you need to use a dark background.
** 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
Still the same.
Still exists in version 6.3.0.0.alpha0+ (x64)
Still exists in version Version: 6.3.0.0.alpha0+ (x64) Build ID: 0f25a3c36f27fd51453b9a9115f236b83c143684 CPU threads: 4; OS: Windows 10.0; UI render: GL; VCL: win; TinderBox: Win-x86_64@42, Branch:master, Time: 2018-11-27_20:06:55 Locale: zh-TW (zh_TW); UI-Language: en-US Calc: threaded
Still exists in version. Version: 6.3.0.0.alpha0+ (x64) Build ID: 0f25a3c36f27fd51453b9a9115f236b83c143684 CPU threads: 8; OS: Windows 10.0; UI render: GL; VCL: win; TinderBox: Win-x86_64@42, Branch:master, Time: 2018-11-27_20:06:55 Locale: zh-TW (zh_TW); UI-Language: en-US Calc: threaded
Exists in v6.1.4.2 OS Windows 7
Yes, this is one problem plaguing me a lot. Can anyone explain how to sort this out? https://hulafrog.com/tracy-manteca-ca/manteca-concrete
(In reply to Ernestas Lukoševičius from comment #0) > 2. Select "Gentoo" word and try to remove underlining - WORKS. Unless I'm missing something, what you say here seems to contradict what's on the Summary: "cannot remove underlining".
(In reply to Kumāra from comment #15) > (In reply to Ernestas Lukoševičius from comment #0) > > 2. Select "Gentoo" word and try to remove underlining - WORKS. > > Unless I'm missing something, what you say here seems to contradict what's > on the Summary: "cannot remove underlining". You're missing other steps. Please read the whole ticket. Other steps explain where we cannot remove underlining. This step is important in setting up the right environment for reproducing the bug. How would you suggest to summarize this ticket then?
(In reply to Ernestas Lukoševičius from comment #16) > (In reply to Kumāra from comment #15) > > (In reply to Ernestas Lukoševičius from comment #0) > > > 2. Select "Gentoo" word and try to remove underlining - WORKS. > > > > Unless I'm missing something, what you say here seems to contradict what's > > on the Summary: "cannot remove underlining". > > You're missing other steps. Please read the whole ticket. Other steps > explain where we cannot remove underlining. This step is important in > setting up the right environment for reproducing the bug. > > How would you suggest to summarize this ticket then? I understand this is a bit complicated. Now here's something to complicate the matter further. Firstly, I followed your steps having created a link in *my own file*, and strangely my Libo 6.0.4.2 (x64) acted perfectly fine. IOW, whatever I do, the link did not revert to the standard "hyperlink look". (Let me add that that I'm here because I had faced the same issue.) Then I tested on your test file. It happened as you said. I copied your text to my own file. Same. BUT, if I change the colour to something other than black, Libo acts perfectly fine. Please try it. Something perhaps worth mentioning: If after step 3 you try to removing the underlining the standard way, nothing happens.
Dear Ernestas Lukoševičius, 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
Reproduce in recent master build: Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 47ca3f1f762352b488d58b3bf23d5776576f1cca CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded (In reply to Kumāra from comment #17) > BUT, if I change the colour to something other than > black, Libo acts perfectly fine. Please try it. Also observed in bug 156578 comment 2 : if the font colour applied is _not_ the original one (before the hyperlink formatting was applied), it behaves as expected.