We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The ComboBox property positionerZIndex has no effect because it's applied to the positioner element, but @zagjs/popper expects custom z-index to be applied to the first child element of the positioner: https://github.com/chakra-ui/zag/blob/9ca9b9edd448071351271465629024ecb1eb80be/packages/utilities/popper/src/get-placement.ts#L185
positionerZIndex
@zagjs/popper
https://github.com/chakra-ui/zag/blob/9ca9b9edd448071351271465629024ecb1eb80be/packages/machines/combobox/src/combobox.connect.ts#L27
skeleton/packages/skeleton-svelte/src/lib/components/Combobox/Combobox.svelte
Line 126 in b1e64c4
The positionerZIndex prop should be applied to the first child element of the positioner element, not to the positioner itself
No response
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Current Behavior
The ComboBox property
positionerZIndex
has no effect because it's applied to the positioner element, but@zagjs/popper
expects custom z-index to be applied to the first child element of the positioner:https://github.com/chakra-ui/zag/blob/9ca9b9edd448071351271465629024ecb1eb80be/packages/utilities/popper/src/get-placement.ts#L185
https://github.com/chakra-ui/zag/blob/9ca9b9edd448071351271465629024ecb1eb80be/packages/machines/combobox/src/combobox.connect.ts#L27
skeleton/packages/skeleton-svelte/src/lib/components/Combobox/Combobox.svelte
Line 126 in b1e64c4
Expected Behavior
The
positionerZIndex
prop should be applied to the first child element of the positioner element, not to the positioner itselfSteps To Reproduce
No response
Link to Reproduction / Stackblitz
No response
More Information
No response
The text was updated successfully, but these errors were encountered: