Consent management: use last consent provided by CMP on timeout (6.29.x)

[dgirardi]

Type of change

• Bugfix

Description of change

This changes the timeout behavior of the consentManagement module (for TCF v2 only).

If after gdpr.timeout the user has not provided consent (and therefore the CMP did not emit a tcloaded or useractioncomplete event), use the last consent data provided by any other CMP event instead of null.

According to the TCF spec, CMPs should always emit at least one event regardless of what the user does.

Note: The addEventListener callback shall be immediately called upon registration with the current TC data, even if the CMP status is loading and the CMP has incomplete TC Data, so that the calling script may have access to its registered listenerId. Furthermore, on every TC String change the callback shall be called unless it is removed via removeEventListener.

In my testing some implementations provide an empty consent string when the user does not dismiss the UI - in that case we ignore the consent object.

Other information

Fixes #7156
Same change for 7.x: #8524

[jsnellbaker]

I think this looks fine. Just to clarify, is there going to be a corresponding change on master as well? Or did the edits made in 7.0 already account for this capture of the tcfData if there was a timeout?

[dgirardi]

there's another pr for master - #8524