Closed j6k4m8 closed 2 years ago
Yeah indexing is a pretty tricky bastard. The thing is that there are a lot of things inside this element taking care of positions, sizes, effects etc.. Did u fix it adding a lower index to the wrapper?
Right — was able to get around this by redoing the rest of the surrounding DOM indexing "on top of" the progressive images.
i added this to my css and now everything looks normal as it was and progressive image still works
.progressive-image {
position: unset !important;
}
Description
.progressive-background-image
'sposition: absolute;
breaks z-indexing with the rest of the document.Expected behavior
Component should act 1-to-1 with tag and sit "under" another element if given a lower z-index
Actual behavior
These components render "on top of" all other components.
Perhaps this is by design? If so, might be worth documenting! Was tricky to track down!