cquanu / github-dark Goto Github PK

Currently the stylesheet applies to any github.com domain such as https://jobs.github.com/.

This can be restricted with a regexp.

What's the issue:

Strikethrough style on deleted code is hard to read. Any way to disable this style?

Steps to reproduce:

View code chances

Screenshots:

Solutions:

Add an option to disable this style. Couldn't find it in CSS

What version is affected by this problem:

GitHub Dark v2.5.0

What's the issue:

Steps to reproduce:

Screenshots:

Solutions:

What version is affected by this problem:

• Rework on Disabled Button
• Rework on Green Button
• Rework on Hover Button

👋 Hello! Just a heads-up — the Github Organization Page header is missing styles.

Steps to reproduce:

Navigate to an Organization page.

Screenshot:

I might be able to make a PR later if I have time later, to add the necessary .org-header. Thoughts?

What version is affected by this problem:

V2.0.0

What's the issue:

Reactions from yourself on issues or PRs are very bright compared to those from other users.

Steps to reproduce:

React to an issue or PR.

Screenshots:

Solutions:

LESS BRIGHT

What version is affected by this problem:

v2.6.0

What's the issue:

Some DIVs are bright white.

Steps to reproduce:

For example, check this project: OpenRA/OpenRA#14191 (review)

Screenshots:

Solutions:

Might be related to:

.Box { background-color: #fff; border: 1px solid #d1d5da; border-radius: 3px; }

What version is affected by this problem:

GitHub Dark 2.0 on Firefox 57.0.2 with the Stylus 1.1.7.8 addon.

What's the issue:

There are around 4000 changes since the current release, which happened 2016

Solutions:

Create a release

What's the issue:

Issue comments have dark text color on dark background.

Steps to reproduce:

Latest version of GitHub Dark on Firefox with GitHub.com

Screenshots:

Solutions:

What version is affected by this problem:

Firefox 70.0b3 (64-bit)
Version 1.0.17
Last Updated September 7, 2019

It is confusing to have both files there and not knowing which one to update when submitting a PR. What about a script that creates one out of the other and a simple note which one to edit?

As can be seen on the following screenshot, there is a white triangle on the Issues section of GitHub that doesn't match the style:

I don't know if there is anything that can be done about this (maybe simply remove it?)

some elements on https://github.com/settings/security are bright white

version: GitHub Dark v2.6.0

What's the issue:

The pop-out description for issues/PRs are still white

Steps to reproduce:

When you scroll down a long issue or a PR, it will appear on the top.

Screenshots:

Thank you very much!

What's the issue:

Readme files and issues in the homescreen are very bright

Steps to reproduce:

Install Github-Dark 2.0

Screenshots:

What version is affected by this problem:

Current, on Stylus

What's the issue:

link to chrome extension is not working. Showing a 404.

https://chrome.google.com/webstore/detail/stylish/fjnbnpbmkenffdnngjfgmeleoegfcffe?hl=en is not correct URL

Steps to reproduce:

Click on the Google Chrome link in the Readme.

Solutions:

Update link with correct URL or if the extension

What's the issue:

Low readability of security history.

Steps to reproduce:

Navigate to the Security tab

Screenshots:

(blacked out some of the more sensitive information)

Solutions:

Change the color property for the CSS rule .mute, .text-gray-dark (note that the property is set as !important).

What version is affected by this problem:

Using 2.1.2

Thank you the theme 👍

Is it possible to make this style compatible with GitLab as well?

That would be awesome!

Hi there,

As a fellow GitHub CSS themer, I thought I'd offer this:

https://github.com/alphapapa/solarized-everything-css

I set up a Makefile that uses Stylus to build the stylesheets, and it makes re-theming so much easier than writing raw CSS. We might even be able to collaborate on the github.styl file, and you could use a dark.styl file to change the colors and fonts. :)

What's the issue:

When hovering on a task-list-item, the background color and the text color are the same, making the text not readable

Steps to reproduce:

Create a task list like the one below, then hover over a list item:

__Methods__
- [ ] mapWidgetAdded
- [ ] mapWidgetRemoved
- [ ] toolbarDrawComplete

Screenshots:

Solutions:

Might be a workaround, I just added the following style for task-list-item on the hover state within the /* Repo | Issues Tab */ section

.task-list-item:hover {
	color: #000
}

it produces the following result:

What version is affected by this problem:

GitHub Dark v2.5.0

Thanks

Thank for providing this great stylesheet. Keep up the good work!

What's the issue?

code samples not-readable

Steps to reproduce

open https://github.com/rusmaxim/angular2-jwt

Screenshots

https://monosnap.com/file/iRipVkH7JAJyFdXhxD3A6uY9TBlGmw

What version is affected by this problem?

v2.0

What's the issue:

Low readability of conflict check in pull requests.

Steps to reproduce:

Visit #24

Screenshot:

What version is affected by this problem:

v2.1.2

What's the issue:

Borders are almost white (#e1e4e8) when you browse Github notifications.
These borders should have the color #304251 instead.

It currently is:

.list-group-item {
    position: relative;
    display: block;
    padding: 8px 10px 10px 40px;
    padding-top: 8px;
    padding-bottom: 10px;
    padding-left: 40px;
    margin-bottom: -1px;
    border: 1px solid #e1e4e8;
}

Steps to reproduce:

Just go to https://github.com/notifications and you'll notice a problem with a border color.

Screenshots:

Solutions:

It would look better with:

.list-group-item {
    position: relative;
    display: block;
    padding: 8px 10px 10px 40px;
    padding-top: 8px;
    padding-bottom: 10px;
    padding-left: 40px;
    margin-bottom: -1px;
    border: 1px solid #304251;
}

What version is affected by this problem:

GitHub Dark 2.0 on Firefox 57.0.2 with the Stylus 1.1.7.8 addon.

What's the issue:

The white background for the review comment header and reply box are very hard to read.

Steps to reproduce:

Go to a PR and look at or create a review with a comment on a line.

Screenshots:

Solutions:

Modify .review-thread-reply and .discussion-item-review .file-header to have a background color matching other headers, i.e. #243447

What version is affected by this problem:

v2.5.0

I may change this myself but don't want to mess with pure css... (that would be great to use something like Sass or Less to generate it...)

What's the issue:

Background color on code ellipsis is too white

#151f29

Steps to reproduce:

• Search for something in a repo (i.e. this):
• Results will be displayed with code ellipsis

Screenshots:

Current:

Proposition:

Solutions:

Change the background to #151f29:

.code-list .divider .blob-num, .code-list .divider .blob-code{
  background-color:#151f29;
}

What version is affected by this problem:

Change for version 2.6

What's the issue:

The background of each section is white, in the Options section of a repo.

Screenshots:

Solutions:

With this code
.Box { background: #1A2632; border-color: #304251; border-width: 1px; }

What version is affected by this problem:

2.6.0

Thanks

On the notifications table, the notification foreground is almost the same as the background making nigh impossible to read them without hovering. Shouldn't/couldn't the foreground be the same light grey as pull requests?

(also, thanks for the styles, really makes github easier on the eyes).

What's the issue:

Markdown images have a background-color so transparent images appear with a darker background than the page itself.

Steps to reproduce:

See any Markdown file with a transparent area (like this one).

Screenshots:

Solutions:

Change the color from --depth-color to transparent.

What version is affected by this problem:

v2.6.3

Stylish says last updated in 2016, yet here are some very fresh commits. Can you update it on stylish too?

What's the issue:

Creating a new repository gives you and empty repository page where the background of the content is bright white. I think it's caused by the background for element
container new-discussion-timeline experiment-repo-nav being white.

Steps to reproduce:

Reproduce by creating a new repository

Screenshots:

Solutions:

What version is affected by this problem:

 * GitHub Dark v2.6.0
 * Copyright 2016 Quan You.
 * GitHub Project (https://cquanu.github.io/github-dark/)
 * Licensed under MIT (https://github.com/cquanu/github-dark/blob/master/LICENSE)
*/

What's the issue:

If you click on show css on the stylish link for this style (https://userstyles.org/styles/128271/github-dark-2-0) it only shows half of the styles when the style is installed, it's missing several lines of css so some elements appear unstyled.

Steps to reproduce:

Install via stylish on Chrome

Screenshots:

Solutions:

Maybe there's a limit on Userstyles.org or some abnormal mistake.

I copy pasted the style from the Github repo and some things that were missing styles now display correctly

What version is affected by this problem:

v2.5.0

Thank you for this

What's the issue:

Highlighted code has low readability under some circumstances, see screenshots.

Steps to reproduce:

No steps needed, just open some code while Github Dark is enabled.

Screenshots:

Mine own .vimrc:

Some Javascript

The white squares in the commit history are destroying the contrast between the colors of the days with commits and those without. I think those squares should be a lot closer to the background (to have the same contrast balance as the official skin of GitHub).

What's the issue?

Diff pages are really hard to read, for example: jslint-org/jslint@f819cf3

First I was worried that It was hard to read the red and green "zones", but then I noticed another zone where the code is not even visible....

Steps to reproduce

Go gere: jslint-org/jslint@f819cf3

Screenshots

What version is affected by this problem?

v2.0 updated right now...

What's the issue?

Inline code blocks like this are not visible in with this plugin.....

Steps to reproduce

Put ` before and after some code.

Screenshots

With the plugin:

Without the plugin:

What version is affected by this problem?

[v2.0]

Possible solution?

.markdown-body code {
    background: #f7f7f7;
    color: #000;
}

It looks like this:

What's the issue:

The text color in the 'Search or jump to...' box in the banner was close to the same color of the background when active/selected. And therefore hard to read.
Background: #151f29
Text: #24292e

Solutions:

Add the following to the CSS:

    .jump-to-field-active{
        color: var(--primary-text-color) !important;
    }

This will change the text color to the primary text color, which is white by default.

What version is affected by this problem:

I'm using v2.6.3

What's the issue:

The issues list on the issue creation page have a white hover.

Steps to reproduce:

Install the latest version using the automatic installer with Stylish/Stylus

Screenshots:

What version is affected by this problem:

v2.6.0

What's the issue:

Low readability of titles on milestones page

Steps to reproduce:

Navigate to https://github.com/angular/angular.js/milestones

Screenshots:

What version is affected by this problem:

v2.1.2

What's the issue:

All the .Box .Box-header... are white instead to be dark

Steps to reproduce:

Just install the lastest version of github-dark 2 using the automatic installer and Stylish/Stylus

Screenshots:

What version is affected by this problem:

v2.6.0

The theme still works, but Stylus reports an error:

	4727	:	1	Unexpected token '}' at line 4727, col 1.

What's the issue:

Unable to read warning text on a repository due to the background colour (#fffccc).

Steps to reproduce:

1. Open a repository with a warning (https://github.com/DefinitelyTyped/DefinitelyTyped)
2. Check the warning text.

Screenshots:

Solutions:

Change the background colour of the class .warning.

What version is affected by this problem:

Verified on version 2.1.1.

Thank you for this, it's been a great help :D

What's the issue:

Hey i'm using the latest version and this problem exists, not sure if this only happens in my machine or not.

Screenshots:

What's the issue:

When I got a new credit card and the Github transaction failed against my old card, I went to change my payment method and found it was really hard to read.

Steps to reproduce:

Settings > Billing. Lot's of hard-to-read text. Click on "Update payment method" and you'll see some more.

Screenshots:

https://s32.postimg.org/6aau4eqhx/git.png

What version is affected by this problem:

v2.1.1

What's the issue:

Internal comments in Security advisories (a brand new github feature) use a orange color to show their internal state (when advisory is not published).
Should use a distinct color for these in this style.

What version is affected by this problem:

2.6.4

Appearance issue in dark mode. I am working on a fix.

What's the issue:

The issue list have a white background

Steps to reproduce:

Install the latest version

Screenshots:

What version is affected by this problem:

v2.6.0

What's the issue:

Filenames in the octotree filebrowser extension are not clearly visible.

Steps to reproduce:

1. Install octotree plugin
2. Visit any repository

Solutions:

Add a a.jstree-anchor and a.jstree-hovered style. Didn't work though.

What version is affected by this problem:

@name           GitHub Dark v2.6.3
@namespace      github.com/cquanu/github-dark
@version        2.6.24

What's the issue:

The empty repo page not readable.

Steps to reproduce:

Create a new repository without any files (readme, license, etc). Github will redirect you to the empty repo page.

Screenshots:

What version is affected by this problem:

GitHub Dark 2.1.2

I find the code unreadable on GitHub because of the colorscheme :|

What's the issue:

Headings are rendered as white text on a white background.

Steps to reproduce:

You can view the readme of this repo. (same as screenshot below)

Screenshots:

Solutions:

Automatically render header text as grey/black.

What version is affected by this problem:

2.6