Skip to content
This repository was archived by the owner on Jun 13, 2024. It is now read-only.

Revert "[a11y-web] adding enabled to button semantics " #220

Closed
wants to merge 1 commit into from

Conversation

nturgut
Copy link
Contributor

@nturgut nturgut commented Jul 20, 2020

Reverts #219

We concluded that the issue is to be fixed in the web engine. Reverting this change.

@nturgut nturgut requested a review from goderbauer July 20, 2020 17:13
@nturgut
Copy link
Contributor Author

nturgut commented Jul 20, 2020

closing the PR: #219 (comment)

@nturgut nturgut closed this Jul 20, 2020
@goderbauer
Copy link
Member

I actually take back my statement that this should be reverted, see #219 (comment).

Since it only adds enabled: true to places where the actual button semantics are disabled via excludeSemantics, adding enabled: true there is actually correct.

Nevertheless, the web engine still has the bug that it should only mark something as disabled when hasEnabledState is set and isEnabled is not set.

Sorry about the confusion.

@guidezpl guidezpl deleted the revert-219-a11y_buttons_web branch July 21, 2020 11:35
clocksmith pushed a commit to clocksmith/gallery that referenced this pull request Jul 23, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants