If you encounter issues feel free to post here, or add them as tickets in trac directly.
You can also keep using the light mode if you prefer, or switch to it if the dark mode has an issue.
I will prepare a patch after receiving enough user feedback to adress issues
Known issues: -Priority for tickets is not seperately highlighted in the ticket lis -File view of txt files is improveable -Ticket box Link + yellow BG contrast is improveable -File view is completely unreadable in some cases -logout link color (Maybe visited link color?) -Preview for creating a new ticket is broken -Contrast or text density may be improveable in areas
Interesting. I had tested this, and in my test only the highlighted line and frame had any issues. I suspect there may be severall different types here at play.
No, css across websites is not compatible. I could use some colors from the discourse css to achieve a uniform look, but personally I don’t like it much.
I would like a bit of opinions/poll, currently the Api docs use Orange as a signal color heavilly, The main site uses orange And blue, and the new trac uses orange and yellow.
Now, as one “idea” here was to make these things a bit more consistent, what would be a good idea going forward:
remove yellow from trac, use only orange?
remove orange from trac as main color (only decoration) use only yellow?
use lightblue for links in trac instead?
Some of these ideas could then propogate back to the api docs.
When trying to do a “preview” for a new ticket, the dark mode makes it totally unreadable. It mostly becomes “white text on white background”, except for some code blocks.
Using the “Dark Reader” on top of current dark theme, makes it better, albeit the “DRAFT” watermark still gets in the way (gets too white).
That is still no actionable feedback. If you have specific suggestions where dark reader improves the contrast or readability feel free to share them, but I don’t see why you bring this up otherwise. The extension has nothing to do with proper browser dark mode support and actually undoes work in that area, in addition it is super configurable So I have absolutely no clue what you might be seeing what you consider better.
The “Main” background color comes from your browser, but the foreground color does not. Should I include the text color in the set of colors from the Browser?
Atleast for ticketboxes or these small info boxes I am going to change the background again, probably inspired by how you altered the Alert, Info, Warning bubbles for the dark mode on the Haiku-os.org site.
Because I have trouble explain all the little details where it makes it better in different parts/pages of Trac. If you could give the extension a go, you could easily see it for yourself, that was my point, sorry if I didn’t made that clear enough.
If you can’t or want to try it for youself, I guess I should try to create side-by-side screenshots (I stil think it would be obvious if you tried yourself, but… OK).
There is not much gained by vague “I think this is better”. In this thread there are severall people who have pointed out specific problems, and those are problems I will adress in a patch release, aswell as problems that I figure out.
I don’t have any interest in trying some random extensions because:
A) It breaks the dark mode, so there is no basis for comparison anymore (especially the “Canvas” Color in CSS comes from your User Agent, that is your webrowser, but It just won’t if dark reader overides it with “something)
B) I have no extensions in WebPositive, so this won’t help me in practice anyway.
C) The extension has countless options that make compareability almost impossible.
In any case, feel free to show specific sections, not already mentioned in the top post or by others here, that can be improved.
