Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Solve Package Page Tooltip Accessibility Bugs and Framework Filter Checkbox List Accessibility Bug #9900

Closed

Conversation

Goodyear2017
Copy link
Contributor

@Goodyear2017 Goodyear2017 commented Apr 3, 2024

Disable Bootstrap popover JavaScript on framework filter and support framework badges, keep the popover classes and layout, add JavaScript function to make the tooltip popup, narrator can read the tooltip.

Add up and down arrow key JavaScript function to make users are able to use arrow keys to move between framework filter mode checkboxes.
Bug links:

@Goodyear2017 Goodyear2017 requested a review from a team as a code owner April 3, 2024 04:59
@Goodyear2017 Goodyear2017 changed the title Solve package page tooltSolve Package Page Tooltip Accessibility Bugs and Framework Filter Checkbox List Accessibility Bugip accessibility bugs and framework filter mo… Solve Package Page Tooltip Accessibility Bugs and Framework Filter Checkbox List Accessibility Bug Apr 3, 2024
@mariaghiondea mariaghiondea requested review from ryuyu and sbanni April 3, 2024 18:31
@Goodyear2017 Goodyear2017 requested a review from ryuyu April 12, 2024 15:07
@@ -1726,3 +1726,36 @@ img.contributors-contributor-avatar {
font-size: 1.1em;
padding: 5px 15px 5px 15px;
}
/* Packages page tooltip */
Copy link
Contributor

Choose a reason for hiding this comment

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

Sometimes we make changes in both css and less file.
@martinrrm could please review this one?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I just move the css to less and compile the css file. BTW, do I need to submit .min file for the js file?

erdembayar
erdembayar previously approved these changes Apr 16, 2024
@Goodyear2017 Goodyear2017 dismissed erdembayar’s stale review April 16, 2024 22:11

The merge-base changed after approval.

@erdembayar
Copy link
Contributor

erdembayar commented Apr 16, 2024

@Goodyear2017
Could you please include before and after screenshots?

@Goodyear2017
Copy link
Contributor Author

@erdembayar Please see the attached videos for before and after.
before.webm
after.webm

@erdembayar
Copy link
Contributor

@erdembayar Please see the attached videos for before and after. before.webm after.webm

It's very hard for me to know difference between 2 videos, just screenshots would have been better.
Also there're .pipelines/NuGetGallery-CI.yml git merge conflict, you may need to rebase your branch with dev branch.

@Goodyear2017 Goodyear2017 force-pushed the lilixie3-1970893-1970906-1987964 branch from 4900eb2 to 7322c13 Compare April 19, 2024 21:38
@@ -1,92 +0,0 @@
name: NuGetGallery CI $(Build.BuildId)
Copy link
Contributor

@martinrrm martinrrm Apr 22, 2024

Choose a reason for hiding this comment

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

Why do we need to remove these files? Or where these changes come from?

@Goodyear2017
Copy link
Contributor Author

@martinrrm I have no clue where the files come from, I will close this PR and make a new one.

@Goodyear2017
Copy link
Contributor Author

I will close this PR and make a new one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants