-
Notifications
You must be signed in to change notification settings - Fork 418
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
Dropdown in dropdown events not passing through due to ::before close pseudoelement #614
Comments
Note my suggested fix fails in the case of having another dropdown as a direct child of details (rather than in a <details class="dropdown">
<summary>Select a phase of matter...</summary>
<details>
<summary>This is a dropdown option</summary>
<ul>
<li>
<label><input type="radio" name="phase" value="gas" /> Gas </label>
</li>
<li>
<label
><input type="radio" name="phase" value="plasma" /> Plasma
</label>
</li>
</ul>
</details>
<details>
<summary>This is a dropdown option</summary>
<ul>
<li>
<label><input type="radio" name="phase" value="gas" /> Gas </label>
</li>
<li>
<label
><input type="radio" name="phase" value="plasma" /> Plasma
</label>
</li>
</ul>
</details>
</details> |
There is another problem in rendering that causes any details elements as children of a dropdown to also render as a dropdown. This is due to this line |
1 similar comment
There is another problem in rendering that causes any details elements as children of a dropdown to also render as a dropdown. This is due to this line |
I have issued a fix for this specific issue here #615 |
Please search for duplicate or closed issues first.
Describe the issue
When placing a dropdown in a dropdown, the click events of elements inside the parent dropdown get masked and non-clickable due to the ::before element that is used as the "click on background to close" handler.
Current Behavior
All elements within a dropdown containing another dropdown non-clickable except for the last child-dropdown.
Expected Behavior
The click events to work as expected
Reproduction URL
https://jsfiddle.net/f9v860hk/3/
Environment
Safari MacOS, probably others.
Suggested fix
obviously more specific selectors would have to be used / written a bit better so as to avoid the use of
!important
, but I just didn't look into it much more yet.The text was updated successfully, but these errors were encountered: