[x] Searched for existing issues and pull requests.
Description
Description of the issue.
Currently, the docs side menu renders navigation elements as <button> elements, rather than <links>. This breaks user expectations regarding behavior (i.e., navigating to new content) and ability to right-click and, e.g., open in a new tab or window.
Preferably, the markup would be refactored to use anchor <a> tags, rather than <button> tags.
Related Issues
Does this issue have any related issues?
No.
Questions
Any questions for reviewers?
No.
Other
Any other information relevant to this issue? This may include screenshots, references, stack traces, sample output, and/or implementation notes.
Demo
If relevant, provide a link to a live demo.
For a live demo of the issue, see
navigate to /docs/api.
right-click on a side menu item.
open the console/inspector.
note the use of button.
Reproduction
What steps are required to reproduce the unexpected output?
In order to reproduce this bug, do the following:
see above.
Expected Results
What are the expected results?
The following results are expected:
I would expect <a> tags.
Actual Results
What are the actual results?
The following are the actual results:
the use of <button> tags.
Environments
What environments are affected (e.g., Node v0.4.x, Chrome, IE 11)? If Node.js, include the npm version, operating system, and any other potentially relevant platform information.
Checklist
Description
Currently, the docs side menu renders navigation elements as
<button>
elements, rather than<links>
. This breaks user expectations regarding behavior (i.e., navigating to new content) and ability to right-click and, e.g., open in a new tab or window.Preferably, the markup would be refactored to use anchor
<a>
tags, rather than<button>
tags.Related Issues
No.
Questions
No.
Other
Demo
For a live demo of the issue, see
/docs/api
.button
.Reproduction
In order to reproduce this bug, do the following:
Expected Results
The following results are expected:
<a>
tags.Actual Results
The following are the actual results:
<button>
tags.Environments
The following environments are affected: