Bug 355615 - Modified highlighting text style selected text colors not applied
Summary: Modified highlighting text style selected text colors not applied
Status: RESOLVED DUPLICATE of bug 307107
Alias: None
Product: kate
Classification: Applications
Component: part (show other bugs)
Version: unspecified
Platform: Kubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: KWrite Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-11-19 23:29 UTC by Eugene Villar
Modified: 2016-05-28 12:36 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Eugene Villar 2015-11-19 23:29:01 UTC 
Whenever you try changing the color of selected text in any highlighting text style (even the "None" text style), it reverts to the default color when you click on "OK" or "Apply"

Reproducible: Always

Steps to Reproduce:
1. In Kate, go to Settings > Configure Kate... > Font & Colors. Then select the Highlighting Text Styles tab.
2. In any Highlight text style (even "None"), modify the selected color of any context.
3. Click on Apply.


Actual Results:  
The modified color reverts back to the previous color.

Expected Results:  
The modified color persists.

I'm using Kate Part 5.15.0 on Kubuntu 15.10
Comment 1 Ivan Shapovalov 2016-03-30 17:12:46 UTC 
I was able to confirm this a while ago, but now it seems to have fixed itself. Please re-check and re-open if needed (stating exact problematic style).
Comment 2 Eugene Villar 2016-03-31 01:46:49 UTC 
Nope. Still doesn't work. I'm still using Kate Part 5.15.0.

I basically tried different variations of the "Steps to Reproduce" and everytime the chosen selected text color or any Context reverts to the default color when pressing "OK" or "Apply".
Comment 3 Dominik Haumann 2016-05-28 12:36:41 UTC 
This was probably fixed in end of October 2015. Please update the KDE Frameworks version to a recent number, e.g. 5.22 or similar. If you still encounter this issue then, please let us know.

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