Bug 116458 - Highlight Color Not Staying The Color I Choose.
Summary: Highlight Color Not Staying The Color I Choose.
Status: RESOLVED DUPLICATE of bug 115291
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
5.4.4.2 release
Hardware: All Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-03-17 18:34 UTC by mckinnonrc
Modified: 2018-03-18 13:29 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description mckinnonrc 2018-03-17 18:34:59 UTC
Description:
If I change the 'Highlight Color' to 'Blue1' on some words that I've highlighted, and then I save it, and then I open up the same document again, then same highlighted words have changed to the darker 'Blue3'.

Steps to Reproduce:
1.Highlight some words, and change the 'Highlight Color' to 'Blue1'.
2.Save the docx.
3.Open the docx, and the 'Highlight Color' to 'Blue1' will now be 'Blue3'.

Actual Results:  
After saving the docx, and opening the docx up again, it changed the selected Highlight Color from Blue1 to Blue3.

Expected Results:
After saving the docx, and opening the docx up again, the selected Highlight Color should still be Blue1 instead of Blue3.


Reproducible: Always


User Profile Reset: No


OpenGL enabled: Yes

Additional Info:
[Information automatically included from LibreOffice]
Locale: en-US
Module: TextDocument
[Information guessed from browser]
OS: Windows 7 64bit
OS is 64bit: Yes

Version: 5.4.4.2 (x64)
Build ID: 2524958677847fb3bb44820e40380acbe820f960
CPU threads: 8; OS: Windows 6.1; UI render: default; 
Locale: en-CA (en_US); Calc: group


User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:59.0) Gecko/20100101 Firefox/59.0
Comment 1 Dieter 2018-03-17 18:43:57 UTC
I suppose it's the same as bug 115291, although bug 115291 is about doc-files.
Comment 2 Buovjaga 2018-03-18 13:29:11 UTC

*** This bug has been marked as a duplicate of bug 115291 ***