-
Notifications
You must be signed in to change notification settings - Fork 56
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
Pagination: responsive part round 2 #1931
base: main
Are you sure you want to change the base?
Conversation
Kudos, SonarCloud Quality Gate passed!
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Possible a11y issue, need to check with our experts.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🚀
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As @MewenLeHo says, there content conveying info display via CSS (< and >) it's a n issue
add a real icon with an aria-hidden=true
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
see my comment before
Will be taken into account with #2008. |
Kudos, SonarCloud Quality Gate passed!
|
The third example for pagination Responsive behaviour looks and behaves as specified. No issues. |
Note: Please transform
- [ ]
into- (NA)
in the description when things are not applicableRelated issues
Superseed #1370.
Description
Add something to handle the mobile responsive part
Motivation & Context
Follow the Orange brand.
Types of change
Live previews
Checklist
Contribution
Accessibility
Design
Development
Documentation
Checklist (for Core Team only)
:not
but already used almost everywhere and should be supported by all browser, I might have done something wrong in here. (https://developer.mozilla.org/en-US/docs/Web/CSS/:not#browser_compatibility)After the merge