feat: add zIndex property

[ArthurFerrao]

What problem is this solving?

We have a situation where more than one Drawer needs to be opened and we need to be able to define which one is on top.

How to test it?

Workspace

Screenshots or example usage:

Gravacao.de.Tela.2024-10-29.as.18.03.47.mov

Describe alternatives you've considered, if any.

Related to / Depends on

How does this PR make you feel? 🔗

![](put .gif link here - can be found under "advanced" on giphy)

[vtex-io-ci-cd]

Hi! I'm VTEX IO CI/CD Bot and I'll be helping you to publish your app! 🤖

Please select which version do you want to release:

• Patch (backwards-compatible bug fixes)

• Minor (backwards-compatible functionality)

• Major (incompatible API changes)

And then you just need to merge your PR when you are ready! There is no need to create a release commit/tag.

• No thanks, I would rather do it manually 😞

[vtex-io-docs-bot]

Beep boop 🤖

I noticed you didn't make any changes at the docs/ folder

• There's nothing new to document 🤔
• I'll do it later 😞

In order to keep track, I'll create an issue if you decide now is not a good time

• I just updated 🎉🎉

[iago1501]

LGTM

[vtex-io-ci-cd]

Your PR has been merged! App is being published. 🚀
Version 0.17.2 → 0.18.0

After the publishing process has been completed (check #vtex-io-releases) and doing A/B tests with the new version, you can deploy your release by running:

vtex deploy [email protected]

After that your app will be updated on all accounts.

For more information on the deployment process check the docs. 📖

[germanBonacchi]

Hi @ArthurFerrao, @hiagolcm and @iago1501,

This weekend, we encountered an issue with one of our clients due to this change.

The native minicart component relies on vtex.store-drawer, and this update introduced an inline z-index style with a default value of 999. This conflicted with our existing styles, which apply a different z-index without !important, causing display issues that prevented users from advancing beyond the minicart.

As a result, our client experienced a half-day of lost sales due to this unexpected conflict.

To prevent similar issues in the future, we kindly ask that changes be properly announced in advance, for example, in VTEX release notes. Having prior knowledge of these updates would allow us to prepare and adapt our clients' stores to avoid potential revenue loss.

Thank you for your attention to this matter.