Sticky Mobile Menu Causing Problems on iOS – query

This topic has 6 replies, 2 voices, and was last updated 5 years, 3 months ago ago by The Watch Strap Co.

  • Avatar: The Watch Strap Co.
    The Watch Strap Co.
    Participant
    August 27, 2020 at 00:13

    Hi there,

    I’m opening this ticket again, as I’m not too sure how this was fixed. Your last ticket said that you removed a few lines of code from one of our pages.

    However, we have added the line of code back and the problem hasn’t returned, additionally the sticky header issue was happening on pages where this code wasn’t ever present and was fixed.

    Was there anything else that you changed? As this code doesn’t seem to have fixed it

    5 Answers
    Avatar: Olga Barlow
    Olga Barlow
    Participant
    August 27, 2020 at 10:28

    Hello,

    Nope, I did not change anything, just that code. Safari does not work well with transitions. It causes the flip effect very often. So, provide us with a link to page where the issue still persists.

    Regards

    Avatar: The Watch Strap Co.
    The Watch Strap Co.
    Participant
    August 27, 2020 at 11:42

    Sorry I didn’t explain correctly.

    The problem is now fixed site-wide, beforehand this affected every page on the website, you only removed the code category page but that fixed it on the checkout page, homepage, contact page etc…

    Thank you

    Avatar: The Watch Strap Co.
    The Watch Strap Co.
    Participant
    August 27, 2020 at 12:45

    I’m just confused as to how that happened, surely something else must have changed too?

    Avatar: Olga Barlow
    Olga Barlow
    Participant
    August 27, 2020 at 14:13

    Hello,

    Nope, really. Maybe just cleared the cache to apply changes, that’s all.

    Regards

    Avatar: The Watch Strap Co.
    The Watch Strap Co.
    Participant
    August 31, 2020 at 16:52

    Hmm strange, thanks though! 🙂

  • Viewing 6 results - 1 through 6 (of 6 total)

The issue related to '‘Sticky Mobile Menu Causing Problems on iOS – query’' has been successfully resolved, and the topic is now closed for further responses

We're using our own and third-party cookies to improve your experience and our website. Keep on browsing to accept our cookie policy.