@unman there is no reason to be upset. This may be a usability issue with the website itself (for example having too much information on the top of the HCL page).
1 Like
unman
July 15, 2021, 11:05am
2
I’m not upset - why would I be? It was a response to OP’s suggestion
There is a usability issue with the website, which I have highlighted -
1 Like
Sorry. Misinterpreted.
opened 01:07PM - 14 Jul 21 UTC
closed 06:38PM - 14 Jul 21 UTC
T: bug
C: website
P: default
diagnosed
<!--(Before filing this issue, please read:
https://www.qubes-os.org/doc/issue-… tracking/
Please use this issue template. Do not delete it.)-->
### Qubes OS version
<!--(The version of Qubes OS you're using (e.g., `R4.0`), available via the
command `cat /etc/qubes-release` in a dom0 terminal.)-->
Irrelevant
### Which [testing](https://www.qubes-os.org/doc/testing/) repositories are you using, if any?
<!--(Please be sure to specify both the names of any enabled testing repos AND
where the testing repos are enabled (i.e., dom0, template, or standalone).)-->
Irrelevant
### Are you providing feedback about a specific package or packages in testing?
<!--(If so, please list the package(s) here and [provide feedback in
`updates-status`](https://www.qubes-os.org/doc/testing/#providing-feedback),
linking to this issue.)-->
No
### Affected component(s) or functionality
<!--(The component or functionality of Qubes OS that is not working as
expected.)-->
qubes-doc
-----
### Brief summary
The HCL has what seems to be a clickable menu on the LHS
The menu does not work, as no indexes are allocated to the buttons.
### How reproducible
<!--(At what rate does the bug occur when the steps to reproduce are
performed?)-->
100%
### Steps to reproduce
1. Go to https://www.qubes-os.org/hcl/
2. Click on "Motherboards"
### Expected behavior
Will jump to motherboard section of hcl
### Actual behavior
Nothing
### Solutions you've tried
### Additional context
<!--(Provide any additional context that might help explain your problem. Also
consider providing terminal output, logs, and screenshots.)-->
-----
### Relevant [documentation](https://www.qubes-os.org/doc/) you've consulted
<!--(Provide a list of any relevant documentation you've consulted. We do not
know what you've already read unless you tell us. If you do not list anything,
we will assume that you haven't read any relevant documentation. If you're not
aware of any relevant documentation, write "None" (or "N/A" if not
applicable).)-->
### Related, [non-duplicate](https://www.qubes-os.org/doc/issue-tracking/#new-issues-should-not-be-duplicates-of-existing-issues) issues
<!--(Provide a list of any related issues of which you're aware. Do not
describe any other unreported bugs, features, or tasks here. We do not know
which issues you've already seen unless you tell us. If there is another issue
that seems like a duplicate, and you did not mention it here, we will assume
that you were not aware of it. If you didn't find any related issues, write
"None found.")-->
@adw is the above fix for this?
adw
July 16, 2021, 8:58pm
4
I think the issue description and commit message are pretty self-descriptive. It’s simply a fix for the buttons not working. It is not a fix for the UX problem of button discoverability (if there is such a problem).
1 Like
Sorry. I correlated the time instead of just the issue title
1 Like