[Resolved] Logo header mobile disappears in chrome and firefox

Home Forums Support [Resolved] Logo header mobile disappears in chrome and firefox

Home Forums Support Logo header mobile disappears in chrome and firefox

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • #697327
    Jorg

    Hi,

    I just installed generatepress and got it to work. Love the simplicity. I have a few questions and one problem.

    1. I do not see the mobile header logo on my mobile in chrome. nor do I see it in firefox when squeezed to mobile size on my mac. in safari I do see the the mobile header logo. How is this possible?
    2. What is the ideal height for the logo? 40px if the menu height is 40 px?
    3. What is the css address of the header logo?
    4. Is there an overview with css addresses?

    #697458
    Leo
    Staff
    Customer Support

    Hi there,

    1. Can you try clearing the caching plugin then disable it first?

    2. Basically yes. There is also default padding added to the logo image which you can adjust with this CSS:

    .mobile-header-navigation .mobile-header-logo img {
        padding: 2px;
    }

    3. Depends on what you are trying to change. Try the selector above first.

    4. No there isn’t unfortunately. Likely too many to list out. If you right click on the element and use browser inspect, you should be able to see all the selectors and CSS code associated with each element.
    Let me know if you need help on identifying any specific ones.

    Let me know if this helps ๐Ÿ™‚

    #697717
    Jorg

    Thanks Leo,

    I managed to position my logo beautiful on mobile. But unfortunately with WP Fastest Cache Premium deactivated.
    So how can I solve that? And is WP Fastest Cache Premium the right plugin for GP?

    #697764
    Jorg

    Strange things happen. Now I do see the mobile header after activating WP Fastest cache again. I will have a look the coming days if this isn’t a provider cache or something.

    #698088
    Leo
    Staff
    Customer Support

    Should be just a caching issue.

    If it happens again, try clearing the plugin cache ๐Ÿ™‚

Viewing 5 posts - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.