-
Notifications
You must be signed in to change notification settings - Fork 13.5k
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
fix(alert, action-sheet): show scrollbar for long list of options #28369
Conversation
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.
Implementation looks good. When merging, I recommend making it clear on the linked issue that scrollbars for action sheet and alert will now show up on non-touch devices, so during development developers should expect to see scrollbars (but not on actual mobile devices)
// Scrollbars on mobile devices will be hidden. | ||
// Users can still scroll the content by swiping. | ||
// If a user has a pointing device, such as a | ||
// mouse or trackpad, then scrollbars will be | ||
// visible. This allows users to scroll the | ||
// content with their pointing device. | ||
// Otherwise, the user would have to use the | ||
// keyboard to navigate through the options. | ||
// This may not be intuitive for users who | ||
// are not familiar with keyboard navigation. |
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.
~ Can we use multi-line comments instead?
core/src/components/alert/alert.scss
Outdated
// Scrollbars on mobile devices will be hidden. | ||
// Users can still scroll the content by swiping. | ||
// If a user has a pointing device, such as a | ||
// mouse or trackpad, then scrollbars will be | ||
// visible. This allows users to scroll the | ||
// content with their pointing device. | ||
// Otherwise, the user would have to use the | ||
// keyboard to navigate through the options. | ||
// This may not be intuitive for users who | ||
// are not familiar with keyboard navigation. |
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.
~ Can we use multi-line comments instead?
core/src/components/alert/alert.scss
Outdated
display: none; | ||
// Scrollbars on mobile devices will be hidden. | ||
// Users can still scroll the content by swiping. | ||
// If a user has a pointing device, such as a |
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.
// If a user has a pointing device, such as a | |
// If a user has a fine pointing device, such as a |
display: none; | ||
// Scrollbars on mobile devices will be hidden. | ||
// Users can still scroll the content by swiping. | ||
// If a user has a pointing device, such as a |
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.
// If a user has a pointing device, such as a | |
// If a user has a fine pointing device, such as a |
…8369) Issue number: resolves #18487 --------- <!-- Please do not submit updates to dependencies unless it fixes an issue. --> <!-- Please try to limit your pull request to one type (bugfix, feature, etc). Submit multiple pull requests if needed. --> ## What is the current behavior? <!-- Please describe the current behavior that you are modifying. --> Web-based users do not get a scrollbar when: - alert has a long list of inputs (this also happens on `ion-select` with the alert interface) - `ion-select` uses the action-sheet interface and has a long list of options This makes it difficult for users to navigate through the options by forcing them to use their keyboards. Some users may also not be used to using their keyboards for navigation. Additionally, this can lead to potential confusion that there are no other options. ## What is the new behavior? <!-- Please describe the behavior or changes that are being added by this PR. --> Web-based users get a scrollbar when: - alert has a long list of inputs (this also happens on `ion-select` with the alert interface) - `ion-select` uses the action-sheet interface and has a long list of options ## Does this introduce a breaking change? - [ ] Yes - [x] No <!-- If this introduces a breaking change, please describe the impact and migration path for existing applications below. --> ## Other information <!-- Any other information that is important to this PR such as screenshots of how the component looks before and after the change. --> The issue was filed for the alert interface but it's also happening on the action-sheet interface. Dev build: 7.5.1-dev.11697570585.1774584d
Issue number: resolves #18487
What is the current behavior?
Web-based users do not get a scrollbar when:
ion-select
with the alert interface)ion-select
uses the action-sheet interface and has a long list of optionsThis makes it difficult for users to navigate through the options by forcing them to use their keyboards. Some users may also not be used to using their keyboards for navigation. Additionally, this can lead to potential confusion that there are no other options.
What is the new behavior?
Web-based users get a scrollbar when:
ion-select
with the alert interface)ion-select
uses the action-sheet interface and has a long list of optionsDoes this introduce a breaking change?
Other information
The issue was filed for the alert interface but it's also happening on the action-sheet interface.
Dev build: 7.5.1-dev.11697570585.1774584d