Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarify Input Exclusion and interactions across iframes #118

Open
mmocny opened this issue Mar 24, 2023 · 0 comments
Open

Clarify Input Exclusion and interactions across iframes #118

mmocny opened this issue Mar 24, 2023 · 0 comments

Comments

@mmocny
Copy link

mmocny commented Mar 24, 2023

Context: a webpage which uses cross-frame communication (e.g. postMessage) to make changes to an another iframe in direct response to interactions.

Visually, this looks exactly as if the shift happened as a direct consequence of the interaction, and if it were all in one frame, we would have excluded it from CLS calculation (via hadRecentInput)


Today the spec states: "An excluding input is any event from an input device which signals a user’s active interaction with the document"

I think the key question for discussion is: Should an interaction from another iframe "signal" this document?

Perhaps for same-origin frames, we could default to signalling all frames.

But for cross-origin, we cannot. Perhaps we could check for the use inter-frame-communication (i.e. postMessage) that happen as a direct consequence of an interaction (either via timer, or task attribution). But, I do not expect we will do this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant