brunnerh
brunnerh
Remove `name` from `RadioTile`. Fixes #972. Probably causes conflicts with pull request #971
The DataTable component uses a spread operation internally which loses all non-enumerated properties and the original type: ```js $: rows = rows.map((row) => ({ ...row, cells: headerKeys.map((key, index) => ({...
Couldn't these props be simplified? `passiveModal` => `passive` `modalHeading` => `heading` `modalLabel` => `label` `modalAriaLabel` => `ariaLabel`
For example in password fields there is this button on the far right which has a tooltip that can break the layout by causing the document content width to be...
[The specification](https://www.carbondesignsystem.com/components/UI-shell-header/usage/) does not mention any specific behavior regarding keyboard navigation of the menus. There are [recommended keyboard interactions for `menu`/`menuitem`](https://www.w3.org/TR/wai-aria-practices/examples/menu-button/menu-button-links.html#kbd_label) elements, though. In particular the basic arrow navigation and...
To me the functionality seems more trouble than it is worth, especially since it is the default. For example I encountered these issues before: - By default the close `X`...
These attributes are meant to be identical for all inputs within a radio button group (the `name` defines the group natively), It would reduce redundancy if the properties were added...
Currently a selection of a radio tile cannot be enforced using native form validation. To use this the same `name` has to be set on all radio inputs along with...
This applies to `datePickerType="single"`, probably to `"range"` as well. In this case the `change` event is fired indirectly via the `onChange` event of flatpickr. Steps to reproduce: 1. Add `DatePicker`...
If a Tooltip with an auto-focused element is positioned e.g. at the bottom edge of the document, clicking it can cause the button that opens the tooltip to move away...