Skip to content
This repository has been archived by the owner on Jun 26, 2019. It is now read-only.

Header vs attribute configuration #14

Open
nbeloglazov opened this issue Oct 31, 2017 · 1 comment
Open

Header vs attribute configuration #14

nbeloglazov opened this issue Oct 31, 2017 · 1 comment

Comments

@nbeloglazov
Copy link

How both configuration interact? For example in the following use case: ad network js creates an iframe and sets transfersize to 300. At the same time website owner returns configuration in header which sets transfersize to 100. Which one wins? The one with stricter limits? Assuming that both ad js and website js register listeners, will they be able to determine which limits were exceeded?

@jkarlin
Copy link
Collaborator

jkarlin commented Nov 1, 2017

Good question. I'm partial to the stricter limit winning, and need to add that to the details section of the explainer.

Yes, the size that was exceeded will be in the event:

Once a threshold is crossed, the bubbling transferexceeded event (a new event type which includes the exceeded threshold and resource category ) is fired on the frame element in the parent frame.

jkarlin added a commit that referenced this issue Nov 1, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants