Skip to content

Conversation

adiessl
Copy link
Contributor

@adiessl adiessl commented Mar 4, 2022

This is meant to clarify that a developer is still responsible to verify the button's "Enabled" state in the "OnClick" event handler.

For further details see https://feedback.telerik.com/blazor/1555442-telerikbutton-disabled-state-can-be-circumvented-to-trigger-onclick

This is meant to clarify that a developer is still responsible to verify the button's "Enabled" state in the "OnClick" event handler.

For further details see https://feedback.telerik.com/blazor/1555442-telerikbutton-disabled-state-can-be-circumvented-to-trigger-onclick
@dimodi dimodi self-assigned this Mar 9, 2022
@dimodi
Copy link
Contributor

dimodi commented Mar 9, 2022

Thanks for the pull request, @adiessl !

I am waiting for a second opinion on this behavior, so I will leave the PR open a bit longer.

@dimodi
Copy link
Contributor

dimodi commented Mar 9, 2022

By the way, have you signed the Contribution License Agreement? I don't see you there, but this is required for us to merge your PR.

@adiessl
Copy link
Contributor Author

adiessl commented Mar 9, 2022

I have signed the Contribution License Agreement.

@dimodi dimodi merged commit 9844727 into telerik:master Mar 9, 2022
dimodi added a commit that referenced this pull request Mar 9, 2022
* Update disabled-button.md

This is meant to clarify that a developer is still responsible to verify the button's "Enabled" state in the "OnClick" event handler.

For further details see https://feedback.telerik.com/blazor/1555442-telerikbutton-disabled-state-can-be-circumvented-to-trigger-onclick

* Update components/button/disabled-button.md

* Update components/button/disabled-button.md

Co-authored-by: Dimo Dimov <961014+dimodi@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants