|
|
Chromium Code Reviews
DescriptionStop the banner pipeline from being triggered if it is already active.
This is a speculative fix for crbug.com/736045. If we tip over the
engagement threshold while the app banner pipeline is active, and we've
already started the banenr checking due to the onload experiment, we
could get into a state where RequestAppBanner is called but we haven't
stopped the previous run.
This CL guards all calls to RequestAppBanner on the banner pipeline not
being active.
BUG=736045
Review-Url: https://codereview.chromium.org/2958473002
Cr-Commit-Position: refs/heads/master@{#482103}
Committed: https://chromium.googlesource.com/chromium/src/+/339d7dc9d0e5c64329105314a52413025b18b89c
Patch Set 1 #
Messages
Total messages: 28 (16 generated)
The CQ bit was checked by dominickn@chromium.org to run a CQ dry run
dominickn@chromium.org changed reviewers: + benwells@chromium.org
PTAL, thanks
Dry run: CQ is trying da patch. Follow status at: https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: Try jobs failed on following builders: android_arm64_dbg_recipe on master.tryserver.chromium.android (JOB_FAILED, https://build.chromium.org/p/tryserver.chromium.android/builders/android_arm6...)
lgtm
The CQ bit was checked by dominickn@chromium.org
CQ is trying da patch. Follow status at: https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: android_arm64_dbg_recipe on master.tryserver.chromium.android (JOB_FAILED, https://build.chromium.org/p/tryserver.chromium.android/builders/android_arm6...)
The CQ bit was checked by dominickn@chromium.org
CQ is trying da patch. Follow status at: https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: android_arm64_dbg_recipe on master.tryserver.chromium.android (JOB_FAILED, https://build.chromium.org/p/tryserver.chromium.android/builders/android_arm6...)
The CQ bit was checked by dominickn@chromium.org
CQ is trying da patch. Follow status at: https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: android_arm64_dbg_recipe on master.tryserver.chromium.android (JOB_FAILED, https://build.chromium.org/p/tryserver.chromium.android/builders/android_arm6...)
The CQ bit was checked by dominickn@chromium.org
CQ is trying da patch. Follow status at: https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: android_arm64_dbg_recipe on master.tryserver.chromium.android (JOB_FAILED, https://build.chromium.org/p/tryserver.chromium.android/builders/android_arm6...)
The CQ bit was checked by benwells@chromium.org
CQ is trying da patch. Follow status at: https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
CQ is committing da patch.
Bot data: {"patchset_id": 1, "attempt_start_ts": 1498264530971440, "parent_rev":
"bf104c1b3d2dfae83774369a9c6a890ad57b9d6e", "commit_rev":
"339d7dc9d0e5c64329105314a52413025b18b89c"}
Message was sent while issue was closed.
Description was changed from ========== Stop the banner pipeline from being triggered if it is already active. This is a speculative fix for crbug.com/736045. If we tip over the engagement threshold while the app banner pipeline is active, and we've already started the banenr checking due to the onload experiment, we could get into a state where RequestAppBanner is called but we haven't stopped the previous run. This CL guards all calls to RequestAppBanner on the banner pipeline not being active. BUG=736045 ========== to ========== Stop the banner pipeline from being triggered if it is already active. This is a speculative fix for crbug.com/736045. If we tip over the engagement threshold while the app banner pipeline is active, and we've already started the banenr checking due to the onload experiment, we could get into a state where RequestAppBanner is called but we haven't stopped the previous run. This CL guards all calls to RequestAppBanner on the banner pipeline not being active. BUG=736045 Review-Url: https://codereview.chromium.org/2958473002 Cr-Commit-Position: refs/heads/master@{#482103} Committed: https://chromium.googlesource.com/chromium/src/+/339d7dc9d0e5c64329105314a524... ==========
Message was sent while issue was closed.
Committed patchset #1 (id:1) as https://chromium.googlesource.com/chromium/src/+/339d7dc9d0e5c64329105314a524... |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
