Howdy, @platinumcode2013!
Thanks for writing in! After looking into this some more, I just wanted to let you know that we’ve moved forward with a bugfix for that that we believe should address the underlying issue, while avoiding any side-effects. The previous solution mentioned does indeed help to wrangle in the overflow of the particles on the Anchor Element; however, it can also create some potential stacking context errors if Elements are overlapping one another. For example, if we had something like this:
Which is three elements laid out sequentially (Button → Alert → Button) and some negative margin on the Buttons to overlap the Alert, using the fix above would result in the following:
Since we don’t want to unnecessarily alter the stacking order if we can, I’ve gone with the following fix that seems to create a new rendering context that respects the overflow: hidden
declaration, without altering the stacking context.
Effectively, we just added transform: translate3d(0, 0, 0);
to a new bit of markup coming out for the Anchor Partial in our next release due to some other changes. I’m unable to test this completely at the moment as my local install has differing markup from what is in the current version, but you could try adding transform: translate3d(0, 0, 0);
to .x-anchor
to see if it helps. If not, you can continue using the fix above as mentioned.
With the next release of the theme, all of this should be taken care of natively and patched up in Safari. Cheers!