Closed vdineva closed 2 years ago
this is another related issue: https://github.com/advthreat/secure-client-forms/issues/902 Seems like in Secure Clients they need to target specific dropdown(s) - but inadvertently are affecting all dropdowns in SecureX and Device Insights. Going forward there will be more apps (e.g. User Insights) added so we need a way not to step on each other's toes
Is your feature request related to a problem? Please describe. We have a few instances in our app (Device Insights) where we have
<ASelect>
withitemTemplate
. See example usage @hereThe problem is that while we can pass in a custom class to the
<ASelect>
element we can't really target the open menu with the items as they are not siblings of the<ASelect>
- it's added as a descendent of the closestAMount
element. If I wrap theASelect
inAMount
- then I get into this issue.Describe the solution you'd like A solution to the above problem would be to add the custom class from
ASelect
to theAMenu
, e.g.in
atomic-react/framework/components/AMenu/AMenu.js
so the consuming app can target this element in their css and not collide with SecureX's styling (ref: https://github.com/advthreat/GLaDOS/issues/3019)