Skip to content

Conversation

@liigo
Copy link
Contributor

@liigo liigo commented Nov 4, 2025

  • Support = shortcut (alongside +) to expand all sections. Already support s and S, Shift or not.
  • Fix search-input's placeholder. The input is auto focused, any key press will be accepted as input not shortcut, current placeholder is missleading.

@rustbot
Copy link
Collaborator

rustbot commented Nov 4, 2025

Some changes occurred in HTML/CSS/JS.

cc @GuillaumeGomez, @jsha, @lolbinarycat

@rustbot rustbot added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-rustdoc Relevant to the rustdoc team, which will review and decide on the PR/issue. T-rustdoc-frontend Relevant to the rustdoc-frontend team, which will review and decide on the web UI/UX output. labels Nov 4, 2025
@rustbot
Copy link
Collaborator

rustbot commented Nov 4, 2025

r? @notriddle

rustbot has assigned @notriddle.
They will have a look at your PR within the next two weeks and either review your PR or reassign to another reviewer.

Use r? to explicitly pick a reviewer

autocomplete="off"
spellcheck="false"
placeholder="Type ‘S’ or ‘/’ to search, ‘?’ for more options…"
placeholder="Search API docs"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd prefer to keep it as is until we come up with a solution on how to tell people that this shortcut exists.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Already told to people by help button.

Copy link
Contributor

@notriddle notriddle Nov 5, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think the current placeholder is a good idea at all.

  • It's shown auto-focused, which is confusing just like liigo says.
  • It's telling you how to open search mode after search mode is already open, which is too late to be useful.

In other words, I agree with the change in this PR.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Discovering a shortcut while using a feature is better than hiding it all the time. The help menu is not a good place to discover shortcuts sadly. Also, when the input is focused, as long as it's empty, the placeholder is displayed (at least on firefox).

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This issue still remains though.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The issue metioned by @GuillaumeGomez exists and could be improved in later PR, without necessarily blocking this PR.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Then revert this change and I'll r+ the PR.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done

["← / →", "Switch result tab (when results focused)"],
["⏎", "Go to active search result"],
["+", "Expand all sections"],
["+ / =", "Expand all sections"],
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We generally avoid adding new shortcuts to not overwrite existing browser/user's shortcuts.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the current + shortcut is not just only +, it's really shift+=.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

User press - (no shift needed), it works. But if he press + (without shift), it not works, this is a bit weird, or not convenient.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It works with just + for me without shift.

Copy link
Contributor

@lolbinarycat lolbinarycat Nov 5, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's not the case for me on firefox, what browser and keyboard layout are you using?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

qwerty and firefox

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Very strange, that's the same here, you don't happen to have any extensions or userscripts that could be changing that behavior, do you?

What's your exact browser version?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Only adblock. Version 143.0.3.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah ok, I understand the issue now. It's because I use the numpad. Well I guess = is fine then.

@liigo
Copy link
Contributor Author

liigo commented Nov 8, 2025

r? @notriddle @GuillaumeGomez

@rustbot
Copy link
Collaborator

rustbot commented Nov 8, 2025

Requested reviewer is already assigned to this pull request.

Please choose another assignee.

@GuillaumeGomez
Copy link
Member

Please squash your commits then r+ time.

Essentially, `=` is "`+` without shift". Current `+` shortcut requires an extra `shift`, unless you use numpad `+`.
@liigo
Copy link
Contributor Author

liigo commented Nov 12, 2025

r? @GuillaumeGomez

@rustbot rustbot assigned GuillaumeGomez and unassigned notriddle Nov 12, 2025
@GuillaumeGomez
Copy link
Member

Thanks!

@bors r+ rollup

@bors
Copy link
Collaborator

bors commented Nov 12, 2025

📌 Commit 9f3d84b has been approved by GuillaumeGomez

It is now in the queue for this repository.

@bors bors added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Nov 12, 2025
@bors
Copy link
Collaborator

bors commented Nov 12, 2025

⌛ Testing commit 9f3d84b with merge 2fcbda6...

@bors
Copy link
Collaborator

bors commented Nov 12, 2025

☀️ Test successful - checks-actions
Approved by: GuillaumeGomez
Pushing 2fcbda6 to main...

@bors bors added the merged-by-bors This PR was explicitly merged by bors. label Nov 12, 2025
@bors bors merged commit 2fcbda6 into rust-lang:main Nov 12, 2025
12 checks passed
@rustbot rustbot added this to the 1.93.0 milestone Nov 12, 2025
@github-actions
Copy link
Contributor

What is this? This is an experimental post-merge analysis report that shows differences in test outcomes between the merged PR and its parent PR.

Comparing 95aeb46 (parent) -> 2fcbda6 (this PR)

Test differences

Show 1 test diff

1 doctest diff were found. These are ignored, as they are noisy.

Test dashboard

Run

cargo run --manifest-path src/ci/citool/Cargo.toml -- \
    test-dashboard 2fcbda6c1a70606bdb09857e01d01fc6229da712 --output-dir test-dashboard

And then open test-dashboard/index.html in your browser to see an overview of all executed tests.

Job duration changes

  1. aarch64-apple: 6779.1s -> 9564.5s (+41.1%)
  2. dist-apple-various: 4011.5s -> 4869.5s (+21.4%)
  3. aarch64-msvc-2: 4763.2s -> 5620.6s (+18.0%)
  4. x86_64-gnu-aux: 5756.6s -> 6675.7s (+16.0%)
  5. dist-x86_64-apple: 7691.1s -> 8859.0s (+15.2%)
  6. x86_64-msvc-2: 7374.2s -> 6402.0s (-13.2%)
  7. x86_64-gnu-stable: 8033.5s -> 7092.7s (-11.7%)
  8. x86_64-gnu-llvm-21-2: 5139.3s -> 5666.5s (+10.3%)
  9. dist-powerpc64le-linux-gnu: 5103.1s -> 5596.4s (+9.7%)
  10. i686-msvc-2: 8373.3s -> 7708.4s (-7.9%)
How to interpret the job duration changes?

Job durations can vary a lot, based on the actual runner instance
that executed the job, system noise, invalidated caches, etc. The table above is provided
mostly for t-infra members, for simpler debugging of potential CI slow-downs.

@rust-timer
Copy link
Collaborator

Finished benchmarking commit (2fcbda6): comparison URL.

Overall result: no relevant changes - no action needed

@rustbot label: -perf-regression

Instruction count

This benchmark run did not return any relevant results for this metric.

Max RSS (memory usage)

Results (primary 1.7%)

A less reliable metric. May be of interest, but not used to determine the overall result above.

mean range count
Regressions ❌
(primary)
1.7% [1.7%, 1.7%] 1
Regressions ❌
(secondary)
- - 0
Improvements ✅
(primary)
- - 0
Improvements ✅
(secondary)
- - 0
All ❌✅ (primary) 1.7% [1.7%, 1.7%] 1

Cycles

Results (secondary 3.7%)

A less reliable metric. May be of interest, but not used to determine the overall result above.

mean range count
Regressions ❌
(primary)
- - 0
Regressions ❌
(secondary)
3.7% [3.5%, 3.8%] 2
Improvements ✅
(primary)
- - 0
Improvements ✅
(secondary)
- - 0
All ❌✅ (primary) - - 0

Binary size

This benchmark run did not return any relevant results for this metric.

Bootstrap: 474.976s -> 474.886s (-0.02%)
Artifact size: 391.06 MiB -> 391.10 MiB (0.01%)

@liigo liigo deleted the better-rustdoc branch November 13, 2025 03:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

merged-by-bors This PR was explicitly merged by bors. S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. T-rustdoc Relevant to the rustdoc team, which will review and decide on the PR/issue. T-rustdoc-frontend Relevant to the rustdoc-frontend team, which will review and decide on the web UI/UX output.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants