You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 13, 2025. It is now read-only.
In MDC Select's DOM structure, the element that receives focus is not the element that ripple/states styles are hooked up to. The element that receives focus is above the ripple surface element.
We have a few components (checkbox, radio, text field) where we override a few MDCRipple adapter methods to detect events on a child element instead of the root, but this would require the opposite, and I'm not sure if that could cause any issues.
OTOH, I'm curious whether we can't simply hook up the ripple to the root element anyway, which might fix multiple ripple/state limitations with MDC Select.
The text was updated successfully, but these errors were encountered:
In MDC Select's DOM structure, the element that receives focus is not the element that ripple/states styles are hooked up to. The element that receives focus is above the ripple surface element.
We have a few components (checkbox, radio, text field) where we override a few MDCRipple adapter methods to detect events on a child element instead of the root, but this would require the opposite, and I'm not sure if that could cause any issues.
OTOH, I'm curious whether we can't simply hook up the ripple to the root element anyway, which might fix multiple ripple/state limitations with MDC Select.
The text was updated successfully, but these errors were encountered: