Upon reviewing the information provided, it appears that the issue may be related to the z-index
property.
One potential solution could be:
In Mobile WebKit and Chrome versions 22 and above, there is a new stacking context created by using position: fixed
, even if the z-index
is set to auto
.
This results in a stacking context hierarchy as follows:
- document root (z-index
0
)
#element
(z-index 9998
)
#element2
(z-index 0
)
.aboveElement
(z-index 9999
)
.belowElement
(z-index 9997
)
It is important to note that direct comparison between z-index values such as 9998
and 9999
may not accurately determine the stacking order. Instead, compare 9999
with 9997
to establish the front-to-back arrangement of elements within #element2
. Once all elements within #element2
are stacked relative to each other, they collectively appear at z-index 0
, positioned behind #element
at z-index 9998
.
To further understand stacking contexts, please refer to Mozilla's documentation on stacking contexts.
Additionally, for changes affecting fixed
position elements in Chrome, read about the updated stacking behaviors in Chrome.