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
The hover state is unintentionally applied to the active accordion section on touch devices (tested on iOS but I believe this will happen on Android also)
While that behaviour is ok, the hover state gets reapplied when you close an accordion section, so you may end up in this situation.
The last closed accordion section looks like it has an active state (actually the hover), the accordion that's open doesn't have a state.
Is there still a trick to stop the hover state appearing on touch devices?
The text was updated successfully, but these errors were encountered:
dashouse
added
the
🐛 bug
Something isn't working the way it should (including incorrect wording in documentation)
label
Jan 16, 2019
The following features are at-risk, and may be dropped during the CR period:
the hover, any-hover, pointer, and any-pointer media features
“At-risk” is a W3C Process term-of-art, and does not necessarily imply that the feature is in danger of being dropped or delayed. It means that the WG believes the feature may have difficulty being interoperably implemented in a timely manner, and marking it as such allows the WG to drop the feature if necessary when transitioning to the Proposed Rec stage, without having to publish a new Candidate Rec without the feature first.
The hover state is unintentionally applied to the active accordion section on touch devices (tested on iOS but I believe this will happen on Android also)
While that behaviour is ok, the hover state gets reapplied when you close an accordion section, so you may end up in this situation.
The last closed accordion section looks like it has an active state (actually the hover), the accordion that's open doesn't have a state.
Is there still a trick to stop the hover state appearing on touch devices?
The text was updated successfully, but these errors were encountered: