Voeg containertiming toe aan zowel de v1- als de v2-toestemmingsbanners

The Consent Studio banner will carry the standard Element Timing and Container Timing attributes, with the identifier consent-banner. This applies to both our v1 and v2 banners, on every theme, on every customer site that loads the banner through Consent Studio.

Nothing needs to change on your side.

What this enables for RUMvision:

• The banner becomes recognisable as a component in paint measurements, under a stable, unbranded name (consent-banner) so measurements stay comparable across sites.

• The attribute is present in the HTML at the moment the browser first paints the banner, so the timing reflects when the banner actually appears, not a later "JavaScript modified it" moment.

• No extra network requests, no added script, no tracking endpoint. It is purely a marker in the HTML; your RUM tool reads it.

To verify, open a page with the banner visible and run this in DevTools:

new PerformanceObserver(l => l.getEntries().forEach(e => console.log(e.identifier, e.startTime, e.element) )).observe({ type: 'container', buffered: true }); 

You should see one entry with identifier consent-banner on the banner element.

Container Timing is currently an experimental API in Chrome (origin trial m148 to m153); without a token on your origin the attribute is simply ignored. Element Timing works today in all Chromium browsers.

Thanks to Erwin Hofman at RUMvision for the input and external validation.