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

Launch layoutbox-invalidate-on-scroll to 0.5% of prod #25730

Merged
merged 1 commit into from
Nov 26, 2019

Conversation

jridgewell
Copy link
Contributor

See #25172

Copy link

@dreamofabear dreamofabear left a comment

Choose a reason for hiding this comment

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

Please create a feature tracking issue with a short test plan that describes (1) new expected behavior with 1-2 sample cases and (2) potential regression surface area. Work with @diantekyrie to verify this.

@@ -34,7 +34,7 @@
"swg-gpay-api": 1,
"hidden-mutation-observer": 1,
"ios-fixed-no-transfer": 1,
"layoutbox-invalidate-on-scroll": 1,
"layoutbox-invalidate-on-scroll": 0.05,

Choose a reason for hiding this comment

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

Why ramp down canary?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

So that canary and rc will have the same fractional experiment. May not be required, since rc and control will have the same fraction.

@jridgewell
Copy link
Contributor Author

#25785

@jridgewell jridgewell merged commit 36d76ff into ampproject:master Nov 26, 2019
@jridgewell jridgewell deleted the invalidate-on-scroll branch November 26, 2019 21:49
caroqliu pushed a commit to caroqliu/amphtml that referenced this pull request Dec 5, 2019
micajuine-ho pushed a commit to micajuine-ho/amphtml that referenced this pull request Dec 27, 2019
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.

3 participants