On fip.fr didomi SDK is set such that on each consent update the page get reloaded. This conflict with the addon as it tries to send "no-consent" on every load.
It now checks the notice visibility beforehand which needed a whole new logic that waits for didomi to be fully loaded.
Also on some malformed sites the notice div is included more that once (eg. iadvize.com)
It seems then that when denying consent only one div get hidden whereas the consent state is actually saved.
So notice div are simply iterated on to properly hide every one.
MathRobin
commented
3 years ago
On fip.fr didomi SDK is set such that on each consent update the page get reloaded. This conflict with the addon as it tries to send "no-consent" on every load. It now checks the notice visibility beforehand which needed a whole new logic that waits for didomi to be fully loaded.
Also on some malformed sites the notice div is included more that once (eg. iadvize.com) It seems then that when denying consent only one div get hidden whereas the consent state is actually saved. So notice div are simply iterated on to properly hide every one.