Properly document hotkeys in generated documentation. #15037
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Continuing from #15012, this makes four changes to the
rustdoc
static files.Click or press 'S' to search, '?' for more options...
to make keyboard hotkeys more apparent (capitalizing theS
to match the help text).main.js
file to use browser-normalized key codes (e.which
, fromjQuery
), instead ofe.keyCode
.?
to be the correct191
instead of188
, so that the hotkey works to bring up search information.tab
andshift+tab
instead ofup
anddown
, as those do not yet work outside of Firefox (see rustdoc: Arrow keys don't always work when searching #15011). Also, adjust the height so it does not cut off the help text.I've also opened up #15038 about the non-functionalup
anddown
functionality, although this does nothing to fix it.