Name the snackbar's renamed hooks in the development skill
Plan step 36. The toast rewrite renamed data-toast and data-toast-action to data-md-toast-snackbar and data-md-toast-action, added data-md-toast on the host and data-md-toast-dismiss on the close button; the skill still told applications to target the old names in tests. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Qwx5USif3wFFmxtHg5U1g9
This commit is contained in:
co-authored by
Claude Opus 5
parent
3b47ebf028
commit
682029b813
@@ -388,7 +388,7 @@ window.addEventListener('app:update', () => location.reload())
|
||||
|
||||
- `description` is M3's second line: the container goes from 48px to 68px (`SnackbarTokens.TwoLinesContainerHeight`), and below `medium` a two-line snackbar with an action wraps the action under the text.
|
||||
- Escape dismisses a snackbar that holds the focus, and **Alt+G** moves the focus to a snackbar that carries an action from wherever the page had it — M3 asks the web for a documented shortcut of that kind, since a snackbar never takes the focus itself. Say so where your users read about keyboard shortcuts.
|
||||
- Hooks: `data-toast` on the snackbar on screen, `data-toast-action` on its action button (`[data-toast]` is absent while nothing shows). Target these in tests, not classes.
|
||||
- Hooks: `data-md-toast` on the host, `data-md-toast-snackbar` on the snackbar on screen (absent while nothing shows), `data-md-toast-action` on its action button and `data-md-toast-dismiss` on its close button. Target these in tests, not classes.
|
||||
|
||||
### `<x-progress>`
|
||||
|
||||
|
||||
Reference in New Issue
Block a user