Based on recent discussion, the <amp-consent> is applying the new check to only allow fullScreen API after user interaction.

The decision was made because of two reasons

1. Security Concern. Avoid full screen embedded iframe without user interaction.
2. UX Concern, Better user experience. A non blocking prompt that takes up to 30vh is recommended based on our UX study. (Having the initial prompt expand right away is used as a workaround to display blocking full screen prompt, but it leads to flicker of the dialog which is not desirable. )

Because of these, the fullScreen API will only be allowed after user has interacted with the CORS iframe. To achieve this we are thinking about checking the document.activeElement. @ampproject/wg-ui-and-a11y Please let me know if that sounds like the right approach.

@MaximePlancke and @andresilveirah Could you please confirm that the Didomi and SourcePoint will continue to work correctly after the change. Thank you very much.

cc @ampproject/wg-analytics