-
Notifications
You must be signed in to change notification settings - Fork 212
[src] view shows lines first and then the code. #264
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
This is an upstream rustdoc bug that should have been fixed by rust-lang/rust#55493, so i'm surprised it showed up on the nightly that rendered these docs ( |
It comes from my add of line numbers and it has been fixed already in rust-lang/rust#55858. |
Is it possible that the documentation will be rebuilt that has been generated in that date region? |
It's not fixed, though. I just updated the nightly used to build crates to |
It is fixed as far as I can tell. For instance: https://doc.rust-lang.org/nightly/src/alloc/string.rs.html#294-296 (but maybe it requires to update to a more recent rustdoc version?) |
@GuillaumeGomez It's still broken on docs.rs though. I rebuilt the crate mentioned in the issue description with the rustdoc i just mentioned, and it still shows the problem - click the link and see for yourself. |
A few things are different in the style apparently:
|
I don't see that difference? I just compared with https://docs.rs/spirv-reflect/0.1.2/rustdoc-20181129-1.32.0-nightly-3e90a12a8.css with https://github.com/rust-lang/rust/blob/d09466ceb1374bd0ff1c490bfd50133b8ca67558/src/librustdoc/html/static/rustdoc.css (after trying to un-minimize the former) and i don't see any significant differences between them. |
Looking further, it seems like the problem is in that CSS selector, |
I looked at |
You mean these rules that are also in nightly? Is there a PR on rust-lang/rust that fixes that? |
This PR added those rules. But it was supposed to fix this very issue. How weird... |
We talked about it on Discord:
I'm planning to work on the latter later today, but if i don't get to it then that's at least what i think the solution should be. |
Still broken for me: https://docs.rs/tokio-udp/0.1.3/src/tokio_udp/socket.rs.html#392-396 |
This is because tokio-udp has been built before this fix was merged. It needs to be rebuilt. This can either be triggered manually by the docs team (afaik) or by pushing a newer version. You probably should open a ticket at tokio-udp and explain it. |
Why can't docs.rs just issue regeneration for all broken crates? Until all the affected crates' docs are updated it's not fixed anyhow. And I've seen a lot of broken crates. |
Clicking on the [src] link for any repo shows you first the line numbers and then the source code.
For example here: https://docs.rs/spirv-reflect/0.1.2/src/spirv_reflect/lib.rs.html#1-601
I get this on Firefox 63.0.3:
The text was updated successfully, but these errors were encountered: