Closed (fixed)
Project:
EU Cookie Compliance (GDPR Compliance)
Version:
7.x-1.14
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
10 Feb 2015 at 17:23 UTC
Updated:
23 Jul 2018 at 20:34 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
stevetweeddale commentedPatch attached. A small amount of refactoring was required to avoid having to trigger the events in multiple code paths.
Comment #2
svenryen commentedHi @stevetweeddale! A lot has changed since you contributed your patch. I tried to implement the same behavior in the latest -dev. Can you have a look at the attached patch and see whether the events trigger correctly?
Comment #3
svenryen commentedI had a problem with the variable names. Ignore #2, here's a patch that should work properly.
Comment #5
svenryen commentedI tested the triggers and found that they all fired, so I'm adding this to -dev. Thanks, stevetweeddale!
Comment #6
svenryen commentedComment #9
jcmiller09 commentedFor the lines removing the popup and triggering the custom event
$('#sliding-popup').remove().trigger('eu_cookie_compliance_popup_close');the remove() method is happening first and not triggering the event since everything is dumped from that element. Putting the trigger() before the remove() allows the event to fire.
Comment #10
jcmiller09 commentedPatch for 7.x-1.23
Comment #11
jcmiller09 commentedComment #12
jcmiller09 commentedIt might also be better to move the event triggers to before the .animate() calls, in case one needs to synchronize other elements on the page. The way it fires now, it has to wait for the animation to complete before the callback fires.
Comment #13
svenryen commentedNice catch, @jcmiller09 ! I'll take a look at the patch!
Comment #16
svenryen commented