title bar of docs displays incorrect version
See original GitHub issueWhat happened:
The browser title bar displays an incorrect version when viewing the docs online. See below - title bar says 0.15.1 but actual version in URL is 0.16.0.
http://xarray.pydata.org/en/stable/
also displays 0.15.1 in the title bar, but I guess is actually showing 0.16.0 docs (?), which is confusing!
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (1 by maintainers)
Top Results From Across the Web
Wrong document title shows when I open a file
Regardless of version of Acrobat, whenever I open a PDF that came originally form a Word file, the wrong file title appears in...
Read more >Troubleshoot Google Docs, Sheets, Slides & Forms error ...
Troubleshoot Google Docs, Sheets, Slides & Forms error message: "Something went wrong". If you get an error message such as "Something went wrong....
Read more >"Close" button on the title bar is displayed incorrectly but can ...
Fixes an issue in which the "Close" button is displayed incorrectly after the SC_CLOSE command is restored in the System menu in Windows...
Read more >PDF18: Specifying the document title using the Title entry in ...
Verify that the title for the document is correctly specified and displayed in the user agent title bar by applying one of the...
Read more >6 fast fixes for common Google Docs problems - Computerworld
So here's the fix: Remember to rely on Docs' robust Version ... and need all the headings to exist in title case in...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
to fix that, we’d need to install the project using
pip
, but RTD uses--upgrade --upgrade-strategy eager
without--no-deps
which means we wouldn’t be able to use version pinning. So I guess we have to wait on RTD?they don’t want to add
--no-deps
to the install command (see https://github.com/readthedocs/readthedocs.org/issues/7345#issuecomment-675587158), but we can work around that by appendingto our environment file (not sure if there’s documentation about this, but there’s an example file). Something similar should also work with requirements files.
I’ll send in a PR.