z-index stacking issues
- Dominant language
- JavaScript
- Stars
- 411
- Forks
- 43
- PR merge metrics
- No merged PRs in 30d
Description
z-index is a classic issue with tooltip/modal libraries I've used. See:
http://codepen.io/matthewlein/pen/zoEvpN
From what I've seen, the only way to make it z-index work as intended is to append to the body, instead of a sibling like you're doing. The body is most likely not in a set z-index context, so it can be reliably set by a developer. Its happened to me plenty of times. `will-change` also creates a new stacking context, making the issue more likely in other unforeseen ways.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating where Huebee appends and positions its tooltip or modal elements, then compare that behavior with the referenced CodePen and the stacking-context cases described in the issue. Done means the picker remains visible above surrounding content, including when ancestors use z-index or will-change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css, javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100