Fix three separate test failures (a11y, Sphinx dev, Sphinx 7.3)#2204
Fix three separate test failures (a11y, Sphinx dev, Sphinx 7.3)#2204trallard merged 9 commits intopydata:mainfrom
Conversation
|
I think all of the test failures are unrelated to this PR except maybe one, docs-checks / build PST docs (ubuntu-latest, 3.9, 6.1) (pull_request), which contains the following in the log output: I'm not sure why |
|
@gabalafou the test says See also: |
|
I have labeled this PR as high impact for two reasons:
|
Do you mean all |
|
I'm re-running the workflows and checking |
Tests against the latest/dev Sphinx version have been seeing: > WARNING: The config value `linkcheck_allowed_redirects' has type `NoneType'; expected `dict'.
|
Nice, thanks @gabalafou And the new lighthouse one (ref GoogleChrome/lighthouse#16404) that we can address separately |
trallard
left a comment
There was a problem hiding this comment.
Thanks @gabalafou this looks good to me, just left one comment that is not a merge-blocker, so will leave it to you to decide if you will leave as is or change.
I think the Lighthouse failures are the result of a combination of two factors. One factor is that our Lighthouse test site is not loading and applying our CSS to the test pages. I think that's probably been true for some time. And then more recently a new check was added to Lighthouse, which you referenced. |
| cp -r docs/examples/kitchen-sink $docs_dir/site/kitchen-sink | ||
| printf "Test\n====\n\n.. toctree::\n\n kitchen-sink/index\n" > $docs_dir/site/index.rst |
There was a problem hiding this comment.
Interesting that this was working without any globbing before.
Good catch tho.
This PR adds the following: - Adds missing traces from #2175 - Updates the `docs` workflow pinned SHA following #2204 (this should be the last change we need to fix the `publish` workflow and have nightly releases back up again) - Updates the `regex` to skip URL checks for `gnu` URLS Closes #2175 --------- Co-authored-by: Tania Allard <tallard@quansight.com>
Fixes #2199.
This should also:
How to test
Run a contrast checker on the following preview build pages.
Check each page both in light mode and dark mode:
Screenshots
The following two screenshots, one for light mode and one for dark mode, show the topic admonition (with higher contrast link) above a regular admonition to show the difference between the regular contrast link color versus the higher contrast link color.
The following two screenshots, one for light mode and one for dark mode, show the four different version-related admonitions, which use higher contrast links, below a warning admonition, which uses regular contrast.
Note that in the version changed admonition (dark mode), the link color is even higher contrast (teal-300) than the other higher contrast links (teal-400).
The following two screenshots show the same table in light and dark mode (all of the links use the higher contrast color).