Skip to content
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

Unexpected empty accesskey attribute set to MultiSelect by default #6289

Closed
veselints opened this issue Feb 15, 2021 · 0 comments
Closed

Unexpected empty accesskey attribute set to MultiSelect by default #6289

veselints opened this issue Feb 15, 2021 · 0 comments
Assignees
Labels
Milestone

Comments

@veselints
Copy link
Contributor

Bug report

MultiSelect renders an empty accesskey attribute on its input, when no access key is passed to its <select> element.

Reproduction of the problem

Run the MultiSelect demo and review the markup of the widget. You will notice its <input> has an accesskey attribute.

Expected/desired behavior

accesskey attribute should not be present

Environment

  • Kendo UI version: 2021.1.119
  • Browser: [all]
@veselints veselints self-assigned this Feb 15, 2021
@kendo-bot kendo-bot added FP: Planned Sync status with associated Feedback Item FP: Unplanned Sync status with associated Feedback Item FP: In Development Sync status with associated Feedback Item and removed FP: Planned Sync status with associated Feedback Item labels Feb 15, 2021
@Dimitar-Goshev Dimitar-Goshev removed the FP: Unplanned Sync status with associated Feedback Item label Feb 16, 2021
@Dimitar-Goshev Dimitar-Goshev added this to the 2021.R1.SP.next milestone Feb 17, 2021
@kendo-bot kendo-bot added FP: Completed Sync status with associated Feedback Item and removed FP: In Development Sync status with associated Feedback Item labels Feb 17, 2021
@Dimitar-Goshev Dimitar-Goshev changed the title Access key attribute should not be present on MultiSelect, when it has no value Unexpected empty accesskey attribute set to MultiSelect by default Feb 17, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants