2023-08-23 08:54:04 -05:00
|
|
|
//@ compile-flags: -Zunstable-options --html-no-source
|
|
|
|
|
|
|
|
|
|
// This test ensures that the `--html-no-source` flag disables
|
|
|
|
|
// the creation of the `src` folder.
|
|
|
|
|
|
|
|
|
|
#![feature(staged_api)]
|
|
|
|
|
#![stable(feature = "bar", since = "1.0")]
|
|
|
|
|
#![crate_name = "foo"]
|
|
|
|
|
|
|
|
|
|
// Ensures that there is no items in the corresponding "src" folder.
|
2024-06-21 07:03:08 -05:00
|
|
|
//@ files 'src/foo' '[]'
|
2023-08-23 08:54:04 -05:00
|
|
|
|
2024-06-21 07:03:08 -05:00
|
|
|
//@ has foo/fn.foo.html
|
rustdoc: redesign toolbar and disclosure widgets
This adds labels to the icons and moves them away from the search box.
These changes are made together, because they work together, but are based on
several complaints:
* The [+/-] thing are a Reddit-ism. They don't look like buttons, but look
like syntax
<https://rust-lang.zulipchat.com/#narrow/stream/266220-t-rustdoc/topic/More.20visual.20difference.20for.20the.20.2B.2F-.20.20Icons>,
<https://github.com/rust-lang/rust/issues/59851>
(some of these are laundry lists with more suggestions, but they all
mention [+/-] looking wrong)
* The settings, help, and summary buttons are also too hard to recognize
<https://lwn.net/Articles/987070/>,
<https://github.com/rust-lang/rust/issues/90310>,
<https://github.com/rust-lang/rust/issues/14475#issuecomment-274241997>,
<https://internals.rust-lang.org/t/improve-rustdoc-design/12758>
("Not all functionality is self-explanatory, for example the [+] button in
the top right corner, the theme picker or the settings button.")
The toggle-all and toggle-individual buttons both need done at once, since we
want them to look like they go together. This changes them from both being
[+/-] to both being arrows.
Settings and Help are also migrated, so that the whole group can benefit from
being described using actual words.
Additionally, the Help button is only shown on SERPs, not all the time.
This is done for two major reasons:
* Most of what's in there is search-related. The things that aren't are
keyboard commands, and the search box tells you about that anyway.
Pressing <kbd>?</kbd> will temporarily show the button and its popover.
* I'm trading it off by showing the help button, even on mobile.
It's useful since you can use the search engine suggestions there.
* The three buttons were causing line wrapping on too many desktop layouts.
2024-08-25 01:11:30 -05:00
|
|
|
//@ has - '//div[@class="main-heading"]/*[@class="sub-heading"]' '1.0.0'
|
|
|
|
|
//@ !has - '//div[@class="main-heading"]/*[@class="sub-heading"]' '1.0.0 · source'
|
2023-08-23 08:54:04 -05:00
|
|
|
#[stable(feature = "bar", since = "1.0")]
|
|
|
|
|
pub fn foo() {}
|
|
|
|
|
|
2024-06-21 07:03:08 -05:00
|
|
|
//@ has foo/struct.Bar.html
|
rustdoc: redesign toolbar and disclosure widgets
This adds labels to the icons and moves them away from the search box.
These changes are made together, because they work together, but are based on
several complaints:
* The [+/-] thing are a Reddit-ism. They don't look like buttons, but look
like syntax
<https://rust-lang.zulipchat.com/#narrow/stream/266220-t-rustdoc/topic/More.20visual.20difference.20for.20the.20.2B.2F-.20.20Icons>,
<https://github.com/rust-lang/rust/issues/59851>
(some of these are laundry lists with more suggestions, but they all
mention [+/-] looking wrong)
* The settings, help, and summary buttons are also too hard to recognize
<https://lwn.net/Articles/987070/>,
<https://github.com/rust-lang/rust/issues/90310>,
<https://github.com/rust-lang/rust/issues/14475#issuecomment-274241997>,
<https://internals.rust-lang.org/t/improve-rustdoc-design/12758>
("Not all functionality is self-explanatory, for example the [+] button in
the top right corner, the theme picker or the settings button.")
The toggle-all and toggle-individual buttons both need done at once, since we
want them to look like they go together. This changes them from both being
[+/-] to both being arrows.
Settings and Help are also migrated, so that the whole group can benefit from
being described using actual words.
Additionally, the Help button is only shown on SERPs, not all the time.
This is done for two major reasons:
* Most of what's in there is search-related. The things that aren't are
keyboard commands, and the search box tells you about that anyway.
Pressing <kbd>?</kbd> will temporarily show the button and its popover.
* I'm trading it off by showing the help button, even on mobile.
It's useful since you can use the search engine suggestions there.
* The three buttons were causing line wrapping on too many desktop layouts.
2024-08-25 01:11:30 -05:00
|
|
|
//@ has - '//div[@class="main-heading"]/*[@class="sub-heading"]' '1.0.0'
|
|
|
|
|
//@ !has - '//div[@class="main-heading"]/*[@class="sub-heading"]' '1.0.0 · source'
|
2023-08-23 08:54:04 -05:00
|
|
|
#[stable(feature = "bar", since = "1.0")]
|
|
|
|
|
pub struct Bar;
|
|
|
|
|
|
|
|
|
|
impl Bar {
|
2024-06-21 07:03:08 -05:00
|
|
|
//@ has - '//*[@id="method.bar"]/*[@class="since rightside"]' '2.0.0'
|
|
|
|
|
//@ !has - '//*[@id="method.bar"]/*[@class="rightside"]' '2.0.0 ·'
|
2023-08-23 08:54:04 -05:00
|
|
|
#[stable(feature = "foobar", since = "2.0")]
|
|
|
|
|
pub fn bar() {}
|
|
|
|
|
}
|
