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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

馃摉 Update data-loading-strategy doc #20004

Merged
merged 1 commit into from Dec 20, 2018

Conversation

zhouyx
Copy link
Contributor

@zhouyx zhouyx commented Dec 20, 2018

No description provided.

@zhouyx zhouyx merged commit 5ced1e8 into ampproject:master Dec 20, 2018
@zhouyx zhouyx deleted the data-loading-doc branch December 20, 2018 17:59
noranazmy pushed a commit to noranazmy/amphtml that referenced this pull request Mar 22, 2019
@@ -91,7 +91,7 @@ If provided, requires confirming the [amp-user-notification](https://www.ampproj

##### data-loading-strategy (optional)

Instructs the ad to start loading when the ad is within the given number of viewports away from the current viewport. You must specify a float value in the range of [0, 3]. By default, the value is 3. Use a smaller value to gain a higher degree of viewability (i.e., increase the chance that an ad, once loaded, will be seen) but with the risk of generating fewer impressions (i.e., fewer ads loaded). If the attribute is specified but the value is left blank, the system assigns a float value, which optimizes for viewability without drastically impacting the impressions. Note, specifying `prefer-viewability-over-views` as the value also automatically optimizes viewability.
Instructs the ad to start loading when the ad is within the given number of viewports away from the current viewport. Without the `data-loading-strategy` attribute, the number is 3 by default. You can specify a float value in the range of [0, 3] (If the value is not specified the value is set to 1.25). Use a smaller value to gain a higher degree of viewability (i.e., increase the chance that an ad, once loaded, will be seen) but with the risk of generating fewer impressions (i.e., fewer ads loaded). If the attribute is specified but the value is left blank, the system assigns a float value, which optimizes for viewability without drastically impacting the impressions. Note, specifying `prefer-viewability-over-views` as the value also automatically optimizes viewability.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Huh? Is the default 1.25 or 3?

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, I get it. If the attribute is not present, the value is 3. If the value IS present (but boolean and not valued) it's 1.25. Don't mind me, just not capable of reading.

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

Successfully merging this pull request may close these issues.

None yet

4 participants