Skip to content
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

Multiselect overlay bug - baseZIndex property is unused #11191

Closed
rinukkusu opened this issue Feb 15, 2022 · 1 comment
Closed

Multiselect overlay bug - baseZIndex property is unused #11191

rinukkusu opened this issue Feb 15, 2022 · 1 comment
Assignees
Labels
LTS-PORTABLE Issue's fix will be ported to supported LTS versions Type: Bug Issue contains a bug related to a specific component. Something about the component is not working
Milestone

Comments

@rinukkusu
Copy link
Contributor

I'm submitting a ... (check one with "x")

[x] bug report => Search github for a similar issue or PR before submitting
[ ] feature request => Please check if request is not on the roadmap already https://github.com/primefaces/primeng/wiki/Roadmap
[ ] support request => Please do not submit support request here, instead see http://forum.primefaces.org/viewforum.php?f=35

Current behavior
It's basically the same Bug as Dropdown overlay bug - baseZIndex property is unused in PrimeNG 12.2.0, but for the MultiSelect component.

When you're in a modal/dialog that's above zIndex 1000, then the Multiselect overlay opens below the dialog, no matter what you set for the baseZIndex property, since, looking at the actual source code, it's not being used. (https://github.com/primefaces/primeng/blob/master/src/app/components/multiselect/multiselect.ts#L684)

Expected behavior
The Multiselect component honors the baseZIndex setting and therefore renders above modals/dialogs with higher zIndex values.

Minimal reproduction of the problem with instructions
Have a modal with zIndex 2000 for instance and add a Multiselect with a baseZindex value that would render it above zIndex 2000.

What is the motivation / use case for changing the behavior?
The multiselect is unusable for containers with a high z-index since the overlay is hidden behind the container.

Please tell us about your environment:

  • Angular version: 13.1.0
  • PrimeNG version: 13.1.1
  • Browser: all

  • Language: all

  • Node (for AoT issues): node --version = 16.13.1

@rinukkusu
Copy link
Contributor Author

@cetincakiroglu duplicate PR, already open PR here: #11192

@yigitfindikli yigitfindikli modified the milestones: 13.Future, 13.2.1 Feb 25, 2022
yigitfindikli added a commit that referenced this issue Feb 25, 2022
Fixed #11191 - Multiselect overlay bug - baseZIndex property is unused
@yigitfindikli yigitfindikli added the LTS-PORTABLE Issue's fix will be ported to supported LTS versions label Feb 28, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
LTS-PORTABLE Issue's fix will be ported to supported LTS versions Type: Bug Issue contains a bug related to a specific component. Something about the component is not working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants