Describe the bug
The text color displayed is not the same as the one that is applied. The color is correctly displayed in the android version but is different in the desktop version
I cannot reproduce this, but the colors selected before the update are incorrectly displayed. However, the newly created ones are properly displayed. This issue only seems to be occuring in the dark theme, default theme displays them properly
Colors selected in the previous versions to be properly displayed
- OS: Fedora Silverblue
- Anytype Version: 0.21.5
The ~/.fonts text and make text both have the same background and foreground colors. The colors for fonts were applied in the previous version and the color for the make text was added now. As you can see in the screenshot, the fonts text color is actually yellow instead of being green
It is fine in the android app
@lynxlove Hi! I was trying to reproduce it in the 21.9 version, but can’t. Do you have this problem now?
Seems to be solved in 0.21.9. Thank you
The same issue is reproducing again in 0.23.0
All highlight colors are yellow in color in dark theme
Apart from that dark theme issue, all the inline code has a grey background inspite of a different background color selected. This can be seen in the video as well
Inline code blocks still have a grey background in the latest version of the anytype app (0.25.0). Not sure if this is intended or a bug since previously it used to have the background color as the one assigned to it. If it is not a bug but was a design decision, I’ll create a new FR for the same
Based on my testing (v0.27.0), I can confirm that both light and dark mode aren’t working correctly.
Code color working, code background color not working:
Code color not working, code background color working:
Issue still in Version: 0.31.48
This report has been added to our issue tracker and received by the Development Team.
This issue has been fixed by the Development Team and will be implemented in an upcoming release.
@Angelo There is slight grey background still visible on the edge (see pic). Is that intended behavior?