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
Seems like the fix is to create a new stacking context on custom-control to get it rendering correctly (ideally z-index, though transform and opacity will also create a new stacking context).
The text was updated successfully, but these errors were encountered:
For some reason, custom checks in CSS columns need a new stacking order to maintain visibility. This PR adds `z-index: 1` to trigger that new stacking order. Since v5's forms are being redone entirely, and we're dropping IE10/11 there, I think this is totally fine to ship with v4 only. Will need to check v5's forms it in Edge though.
Fixes#29607.
…30810)
For some reason, custom checks in CSS columns need a new stacking order to maintain visibility. This PR adds `z-index: 1` to trigger that new stacking order. Since v5's forms are being redone entirely, and we're dropping IE10/11 there, I think this is totally fine to ship with v4 only. Will need to check v5's forms it in Edge though.
Fixes#29607.
Co-authored-by: XhmikosR <xhmikosr@gmail.com>
Windows 10
Reproduced on IE Edge, IE 11 and IE 10
Screenshot of issue:
Codepen reproduction:
https://codepen.io/mattywong/full/NWWajYJ
Seems like the fix is to create a new stacking context on custom-control to get it rendering correctly (ideally z-index, though transform and opacity will also create a new stacking context).
The text was updated successfully, but these errors were encountered: