• Resolved zil1

    (@zil1)


    Hi,

    I use Q2W3 Fixed Widget on my website for my two sidebars and it’s perfect, but there’s a strange bug with Google Chrome (all the other browsers work correctly): when I click on my table of content on the left sidebar, in order to go directly to a specific section, my sidebars go up, the upper sections disappear totally, and a big white space appear at the bottom of the page (it’s quite difficult to describe, I can send you a picture if you want). And the strangest is that the problem is not visible on all computers, and not all the time!
    I disabled the following CSS rules as I read on your website but nothing happened:
    webkit-backface-visibility:hidden;
    webkit-transform: translate3d(0,0,0);

    Can you help me please? I love your plugin and this bug is so a pity!

    The page I need help with: [log in to see the link]

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Thomas Maier

    (@webzunft)

    Hi zil1,

    thanks for reaching out.

    I caught the behavior you described the second time I loaded the page in Chrome.

    There is a JavaScript issue in the browser console:

    Error: Syntax error, unrecognized expression: .seulement.

    It relates to this line in your code:

    $(".seulement." + $niveau ).removeClass("su-spoiler-closed");

    I cannot say if it is relevant, but please try to resolve it. Any critical JavaScript might have an effect on the fixed widget script.

    I also saw that you are using jQuery 3.4.1. This is not the jQuery version coming with WordPress by default. Could you please test if disabling it helps?

    Both are general suggestions. How did you determine that the issue is related to Fixed Widget after all?

    Thanks,
    Thomas

    Thread Starter zil1

    (@zil1)

    Hi Thomas,

    Thank you for your answer.

    Actually you’re right: this issue is not related to Fixed Widget at all! I read on your website that there could be a problem with Google Chrome, and as my sidebar was in a fixed widget, I thought that it came from your plugin… But after my post I saw that other links out of a fixed widget gave the same bug, and finally it seems to be a conflict between another plugin and my theme. So please forgive me, I was wrong writing to you! I’m quite a novice in solving this kind of issues. For your information, I have tried your two suggestions and it did’nt work, but thank you for your time.

    Sylvain

    Plugin Author Thomas Maier

    (@webzunft)

    Hi Sylvain,

    you are most welcome and no problem. I hope you will find a solution to the issue.

    Good luck!

    Thomas

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘Bug with Chrome’ is closed to new replies.