• Resolved wpwebdevj

    (@wpwebdevj)


    Audit usage of navigator.userAgent, navigator.appVersion, and navigator.platform
    
    A page or script is accessing at least one of navigator.userAgent, navigator.appVersion, and navigator.platform. In a future version of Chrome, the amount of information available in the User Agent string will be reduced.
    To fix this issue, replace the usage of navigator.userAgent, navigator.appVersion, and navigator.platform with feature detection, progressive enhancement, or migrate to navigator.userAgentData.
    Note that for performance reasons, only the first access to one of the properties is shown.
    1 source
    autoptimize_2a7e64f….js:1
    Learn more: User-Agent String Reduction

    When I disable Autoptimize then this warning disappears.

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

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Optimizing Matters

    (@optimizingmatters)

    That’s part of lazysizes.js, which AO uses for its lazyload implementation. I reviewed the code and Chrome not supporting navigator.userAgent will have no impact.

    If you don’t want the warning simply disable lazyload in AO and the warning will go away 🙂

    frank

    Thread Starter wpwebdevj

    (@wpwebdevj)

    Yes, after removing the autoptimize_filter_imgopt_lazyload_js_noptimize filter I can see where it’s coming from now. Thanks.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Browser console warning when Autoptimize is enabled’ is closed to new replies.