silverwind

I'd focus on making the `github` theme look good. The other two are rarely used and you can't make them perfect because of different tokenizers used.

Maybe we should exclude that page from styling. We generally don't have the resources to keep up with GitHub's ever-changing fancy marketing sites.

That's not really a secondary color, we actually have it as a regular blue. CSS provides no method to modify a color (besides the dropped [color-mod proposal](https://github.com/w3c/csswg-drafts/issues/813)), and this blue...

Indeed, once we have implemented [CSS variables](https://github.com/StylishThemes/GitHub-Dark/issues/1096), users can easily replace all colors in simple add-on userstyles. Let's drop the color option after that one is done.

It is but you have to agree that the page looks odd with non-blue colors in some places. If a feature can't deliver quality, it's better to remove it.

You want to make the white/grey text colors customizable? I don't think this is a easy undertaking.

Any link to a page containing this?

Ah I see, should have mentioned issue. I was thinking wiki.

This is a hard one. If we hide one button, we risk having none appear after this issue is fixed. Certainly a GitHub bug but only visible with our padding...

I don't see any outlines in Firefox, even if I manually add `:focus`. Is there a user agent rule that Chrome applies (not sure if it's possible in Chrome Devtools...