-
-
Notifications
You must be signed in to change notification settings - Fork 32.4k
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
[core] Batch small changes #19016
[core] Batch small changes #19016
Conversation
Remove the polyfils to uncover potential issues and give more confidence when authoring components. Developers should expect our demos to provide the same level of quality than the source. If we need a polyfill to make the docs run, something is probably off.
e123868
to
67fceb4
Compare
Details of bundle changes.Comparing: 83fb7f4...d960cb9
|
67fceb4
to
82e6177
Compare
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.
Please move everything affecting published (to npm) code to a separate PR for a proper entry in version control (revertability, changelog etc). Particularly the Snackbar change.
@eps1lon I have updated the Snackbar accessibility visibility guidelines to be more accurate. Thanks for the feedback I'm sorry, I'm not sure to follow. The changes are aimed to be low impact/risk. Revertability and changelog should be "dimensions" we can ignore. Do you see any significant changes that we should worry about? What's the concern with the snackbar? |
Co-Authored-By: Matt <[email protected]>
@@ -86,27 +86,20 @@ It also enables you to **stack** them on top of one another (although this is di | |||
|
|||
(WAI-ARIA: https://www.w3.org/TR/wai-aria-1.1/#alert) | |||
|
|||
- Since alerts are not required to receive focus, content authors should not require users to close a Snackbar if the role is set to `alert` through the SnackbarContent `role` prop. This is the default role. | |||
- If a Snackbar requires focus to close it, then content authors should use the `role` of `alertdialog`. | |||
- By default, the toast won't auto-hide. However, if you decide to use the `autoHideDuration` prop, it's recommended giving users [enough time](https://www.w3.org/TR/UNDERSTANDING-WCAG20/time-limits.html). |
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.
- By default, the toast won't auto-hide. However, if you decide to use the `autoHideDuration` prop, it's recommended giving users [enough time](https://www.w3.org/TR/UNDERSTANDING-WCAG20/time-limits.html). | |
- By default, the Snackbar won't auto-hide. However, if you decide to use the `autoHideDuration` prop, it's recommended giving users [enough time](https://www.w3.org/TR/UNDERSTANDING-WCAG20/time-limits.html). |
(A toast is an Android system notification)
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.
I believe a toast is the generic name for the snackbar (ignoring Material Design language). You can verify this proposition by benchmarking the other design systems.
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.
http://programmerguru.com/android-tutorial/snackbar-vs-toast/
https://stackoverflow.com/questions/34432339/android-snackbar-vs-toast-usage-and-difference
For your SEO kick, you could add sometimes (mistakenly 😉) referred to as a "toast" to the description. But best not to cause confusing by using a different name in the body text.
I have reverted the snackbar's changes and I'm moving them to a dedicated pull request because they seem to raise an ongoing flow of concerns. |
083b7f6
to
d960cb9
Compare
The fix applied in mui#19016 is no longer needed
Developers should expect our demos to provide the same level of quality as the source.
If we need a polyfill to make the docs run, something is probably off.
[Snackbar] Improve accessibility edb25bf: Leverage https://medium.com/@sheribyrnehaber/designing-toast-messages-for-accessibility-fb610ac364be. The aria-describedby seems to originate from the initial implementation, a long time ago, after a benchmark, and listening to VoiceOver announcement, I believe we can remove it, and simplify the demos :). If it's needed, then it would be great to explain why in the accessibility subsection of the docs page.