| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
FYI As a color blind person, I don't see the difference between "Borrowed reference" and "New reference" colors in the light mode. Well, I'm also color blind, so my opinion may not matter :-) In the dark mode, I see clearly that the two colors are very different. |
Sorry, something went wrong.
|
If you’re reusing existing colors, how about you centralize their definition as a CSS variables and then use it from both your new CSS rules and the old ones that originally defined the color? |
Sorry, something went wrong.
|
Good idea, shall we also replace the pale green for the other "Return value" with the "New in version" green? The light mode ones are much closer, but we could replace one with the other here too? |
Sorry, something went wrong.
Sorry, something went wrong.
There was a problem hiding this comment.
I don't have a strong opinion regarding naming, but I like the change! Personally, I would prefer borrowed references to be labelled as "bad", but that is a different discussion.
Sorry, something went wrong.
|
This is now deployed: https://docs.python.org/3/c-api/exceptions.html |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Follow on from python/cpython#117926.
Currently light green is used for all return types:
For example: https://docs.python.org/3/c-api/exceptions.html
A borrowed reference is not necessarily a "bad" thing, but we may want to use something other than green that indicates it's "good", to indicate they should be treated with care.
This PR uses the same yellow/orange colour as the "Changed in version x.y" text in #185 - I've already checked the contrast ratios in that PR and both meet WCAG AAA. By using the same colour, it will be easier to check/change when we audit.
For example: https://python-docs-theme-previews--188.org.readthedocs.build/en/188/c-api/exceptions.html#querying-the-error-indicator