Forum Replies Created

Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter Bruno

    (@heeroyui)

    yes

    I no longer have the problem when I enable the “Enable lazy loading of native browser” option and delete the following line: 

    // For JavaScript code blocks, use wp_kses_post which allows safe content
    printf( '<script type="text/javascript">%s</script>', wp_kses_post( $sanitized_js ) );

    (but if the code remains, it will return in the next update)

    Thread Starter Bruno

    (@heeroyui)

    Basic Options

    ✔ Cache System
    ✔ Mobile Cache
    ✔ Gzip compression
    ✔ Browser cache
    ✔ Cross origin Safe links

    File Optimization

    ✔ HTML minify
    ✔ CSS minify (removes whitespace + font)
    ✔ Include inline CSS
    ✔ Combine CSS
    ✔ JS minify
    ✔ Include inline JS
    ✔ Combine JS

    Preload

    ✔ Preload Links

    Advanced options

    ✔ Disable emoji
    ✔ Host Files Locally (Google Fonts)

    The rest is not active.

    If I enable lazy loading of images (images + iframe + video + native browser), I have the problem.
    I just saw that the problem comes from the “Enable lazy loading of native browser” option. I never had this problem before with the option enabled.

    I have same problem with all my websites with a # (anchor) in the href

    https://ibb.co/tpyLnfc
    https://ibb.co/VT4Tcvq

    • This reply was modified 1 year, 6 months ago by Bruno.
    • This reply was modified 1 year, 6 months ago by Bruno.
Viewing 3 replies - 1 through 3 (of 3 total)