fix(component-testing): Search spec overflowing

[dmtrKovalenko]

When we have a lot of specs:

Before:

After:

[cypress-bot]

Thanks for taking the time to open a PR!

• Create a Draft Pull Request if your PR is not ready for review. Mark the PR as Ready for Review when you're ready for a Cypress team member to review the PR.
• Become familiar with the Code Review Checklist for guidelines on coding standards and what needs to be done before a PR can be merged.

[cypress]

---

Test summary

3984 • 0 • 49 • 2 • 0

---

Run details

Project	cypress
Status	Passed
Commit	e8599d6
Started	Mar 17, 2021 3:20 PM
Ended	Mar 17, 2021 3:29 PM
Duration	09:45 💡
OS	Linux Debian - 10.5
Browser	Chrome 83

View run in Cypress Dashboard ➡️

---

This comment has been generated by cypress-bot as a result of this project's GitHub integration settings. You can manage this integration in this project's settings in the Cypress Dashboard

[agg23]

Unless you have a z-index of 9, this is an incorrect assignment. z-index is entirely based on stacking context, so if you're an old-school JS dev, setting z-index: 1000 or whatever didn't actually do anything special.

Most likely (without pulling down the branch and trying it myself) you want z-index: 1

[dmtrKovalenko]

No. You can pull the branch and debug it yourself. I prefer tailwind style of indexing with a 10x. Previous is 1 new is 10 next is 100