Jakub Górka

InputNumber: onChange and onValueChange events are not triggered when using keyboard shortcut for "cut" action

1

### Describe the bug The onChange and onValueChange events associated with an input field fail to trigger in two scenarios: 1. When attempting to cut all numbers using a keyboard...

### Describe the bug In Safari, when a small fixed width is applied to a dropdown, the scrollbar is not rendered correctly. The width of the dropdown is not big...

SplitButton: aria-controls references ID that doesn't exist in DOM until menu is oopened

1

### Describe the bug The SplitButton component sets an aria-controls attribute on the button element pointing to an ID (e.g., pr_id_256_overlay) that is not present in the DOM until the...

### Describe the bug The DataTable component fails accessibility requirements (E950, E951 and E8791). An element with role='table' must have an accessible name. Setting name via props doesn't set it...

### Describe the bug The MultiStateCheckbox component fails accessibility requirements. A form field element has neither an id nor a name attribute. This might prevent the browser from correctly autofilling...

### Describe the bug Passing a custom `header` element to the Column always renders it inside the ``, which is often not correct for accessibility. A lot of elements can...

### Describe the bug The InputNumber component fails accessibility requirements, when a max range is provided. The input element with `type="text"` should not have `max` attribute. Not sure if this...

### Describe the bug The ListBox component fails accessibility requirements. The element with role="listbox" does not have an accessible name. This can be observed in the official documentation: https://primereact.org/listbox/ Example...

### Describe the bug The MultiSelect component fails accessibility requirements. The input element with role="combobox" does not have an accessible name. This can be observed in the official documentation: https://primereact.org/multiselect...

### Describe the bug The DOM element order in FloatLabel is incorrect. The element comes after the instead of before it. This affects accessibility and is inconsistent with expected HTML...