[Violation] ‘message’ handler took 157ms

  • Resolved rpb1001

    (@rpb1001)


    4 years, 5 months ago

    Hello,
    You can’t see an error on the linked page, and this is impossible for you to do anything about! But, I’ll just report it anyway, and you can close as you see fit.
    I started getting “Aw Snap” issues in the browser and seeing “Violation” issues in the console… though hard to get further than that.


    After disabling from end plugins, it came down to being able to reproduce the issue by switching “Enable safe mode” on an off on the complianz plugin.
    I am assuming it is interacting with an iFrame on the page (facebook) or some other Javascript that is dropping a cookie.
    If you have any suggestions for debugging that, I would love to hear.
    Thanks!

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

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Contributor Rogier Lankhorst

    (@rogierlankhorst)

    Hi @rpb1001,

    Thanks for reporting your issue. I couldn’t reproduce this on our own demo environment yet. Possibly what Chrome is complaining about, is the cookieblocker reactivating scripts.

    What exactly is the violation message you see?

    What Complianz does, is preventing third party cookies from being set by changing the <script type=”text/javascript” to <script type=”text/plain”. For iframes, the src is moved to a data-src attribute.

    The result is that, without consent, no scripts or frames are loaded, and so no cookies are placed.

    When the user consents to cookies, these scripts are then dynamically activated again. This happens after the page has fully loaded, which effectively works as a type of lazy loading.

    I suspect such behaviour is not what Chrome expects, causing the warnings. If I can reproduce it consistently, I might be able to tell you more.

    Off topic: I see you have also another cookiebanner active, with a dead link in it. So a user has to click two banners away.

    Thread Starter rpb1001

    (@rpb1001)

    Thanks a lot for the explanation – appreciated. I can’t remember what I did now and have not seen the error for some time. I suspect I uninstalled Complianz! When I review this in January I will come back if I find the error again.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘[Violation] ‘message’ handler took 157ms’ is closed to new replies.