• Resolved one2many

    (@one2many)


    I noticed that autoptimize is causing a significant number of errors to be logged in the chrome dev console. It appears that Chrome 73 adjusted the way it handles passive event listeners: https://www.chromestatus.com/features/6662647093133312. As I scroll through down my website, I see 50-100 of these messages: “[Intervention] Unable to preventDefault inside passive event listener due to target being treated as passive.”

    It appears that the event.PreventDefault causes this error in the following code (right above Jquery Tiny Pub/Sub)

    1.2 < Math.abs(deltaX) && (deltaX *= options.stepSize / 120);
    1.2 < Math.abs(deltaY) && (deltaY *= options.stepSize / 120);
    scrollArray(overflowing, -deltaX, -deltaY);
    event.preventDefault()
    });
    addEvent(“mousedown”, function(event) {
    activeElement = event.target
    });
    addEvent(“load”, init)

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

    (@optimizingmatters)

    well, Autoptimize doesn’t add code by or off itself, but aggregates the JS added by your plugins/ your theme. you can try to identify which plugin (or if your theme) is adding this by appending ?ao_noptimize=1 to the URL and seeing what JS-file Chrome singles out in that case, after which you can ask the developer of that to look into the warnings.

    hope this helps,
    frank

Viewing 1 replies (of 1 total)

The topic ‘PreventDefault’ is closed to new replies.