The Footer section is not responsive for mobile screen

This topic has 5 replies, 3 voices, and was last updated 2 years, 4 months ago ago by roy

  • Avatar: roy
    roy
    Participant
    November 26, 2021 at 22:31

    I have two questions on the responsive for mobile screen.
    1. I used static block Foot-niche-market02-Elementor as the Footer, After just changing the brand logo, the footer layout for the mobile screen crashed.

    2. How to setting different font-size for mobile screen? Since normally the text for the desktop is too large for the mobile screen and it seems that the font-size is not responsive.

    Please, contact administrator
    for this information.
    4 Answers
    Avatar: Rose Tyler
    Rose Tyler
    Support staff
    November 27, 2021 at 11:23

    Hello,

    1/ https://prnt.sc/20xlguh , clear cache before checking the result.
    2/ https://elementor.com/help/mobile-editing/

    Regards

    Avatar: roy
    roy
    Participant
    November 29, 2021 at 16:03

    Hi, I watched the elementor tutorials video on responsive settings. But in my case when changing heading text size for the mobile view, the desktop view always has the same text size. This is different from the tutorials. You can try it by selecting any Heading for edit on the home page.
    Thanks!

    Please contact administrator
    for this information.
    Avatar: Olga Barlow
    Olga Barlow
    Support staff
    November 29, 2021 at 16:21

    Hello,

    I changed the banners titles and it works https://prnt.sc/20z8e25
    Changed the headings https://prnt.sc/20z8iu8 and it also works https://prnt.sc/20z8om1
    So, don’t understand your issue. Provide us with video of the problem for better understanding. You can use Recordit tool to create video.

    Regards

    Avatar: roy
    roy
    Participant
    November 29, 2021 at 16:43

    It works now. Thank you!

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

The issue related to '‘The Footer section is not responsive for mobile screen’' 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.