|
|
Created:
3 years, 11 months ago by Alexei Svitkine (slow) Modified:
3 years, 11 months ago Reviewers:
Ted C CC:
chromium-reviews, agrieve+watch_chromium.org Target Ref:
refs/pending/heads/master Project:
chromium Visibility:
Public. |
DescriptionFix blank NTP bug on Clank.
This was a result of the FRE refactor work for first run experiments,
which had moved FirstRunActivity creation to be before native init.
As a result of that, the removeBackground() ChromeTabbedActivity ended
up happening when the activity was not foreground, which apparently
caused the bug.
This change fixes it by making the removeBackground() call happen
later, when the ChromeTabbedActivity is visible. The logic is such
that we do it once both native init and window focus events have
been received.
BUG=673831
Committed: https://crrev.com/928bfdc6404ea14bc71c28ef3e483453c34d0c52
Cr-Commit-Position: refs/heads/master@{#441378}
Patch Set 1 #
Total comments: 2
Patch Set 2 : Address nit. #Messages
Total messages: 17 (11 generated)
Patchset #1 (id:1) has been deleted
asvitkine@chromium.org changed reviewers: + tedchoc@chromium.org
The CQ bit was checked by asvitkine@chromium.org to run a CQ dry run
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: This issue passed the CQ dry run.
lgtm https://codereview.chromium.org/2613573003/diff/20001/chrome/android/java/src... File chrome/android/java/src/org/chromium/chrome/browser/ChromeActivity.java (right): https://codereview.chromium.org/2613573003/diff/20001/chrome/android/java/src... chrome/android/java/src/org/chromium/chrome/browser/ChromeActivity.java:1047: private void possiblyRemoveWindowBackground() { tiniest of nits, but I think we use "maybe" instead of "possibly" more often to represent this concept in java.
https://codereview.chromium.org/2613573003/diff/20001/chrome/android/java/src... File chrome/android/java/src/org/chromium/chrome/browser/ChromeActivity.java (right): https://codereview.chromium.org/2613573003/diff/20001/chrome/android/java/src... chrome/android/java/src/org/chromium/chrome/browser/ChromeActivity.java:1047: private void possiblyRemoveWindowBackground() { On 2017/01/04 00:30:04, Ted C wrote: > tiniest of nits, but I think we use "maybe" instead of "possibly" more often to > represent this concept in java. Done.
The CQ bit was checked by asvitkine@chromium.org
The patchset sent to the CQ was uploaded after l-g-t-m from tedchoc@chromium.org Link to the patchset: https://codereview.chromium.org/2613573003/#ps40001 (title: "Address nit.")
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": 40001, "attempt_start_ts": 1483542579134640, "parent_rev": "33dc4240b9e726e95dd733283c92f4f6c3f6d326", "commit_rev": "f6f56907cf3a83859149613237be593cfb63b4e5"}
Message was sent while issue was closed.
Description was changed from ========== Fix blank NTP bug on Clank. This was a result of the FRE refactor work for first run experiments, which had moved FirstRunActivity creation to be before native init. As a result of that, the removeBackground() ChromeTabbedActivity ended up happening when the activity was not foreground, which apparently caused the bug. This change fixes it by making the removeBackground() call happen later, when the ChromeTabbedActivity is visible. The logic is such that we do it once both native init and window focus events have been received. BUG=673831 ========== to ========== Fix blank NTP bug on Clank. This was a result of the FRE refactor work for first run experiments, which had moved FirstRunActivity creation to be before native init. As a result of that, the removeBackground() ChromeTabbedActivity ended up happening when the activity was not foreground, which apparently caused the bug. This change fixes it by making the removeBackground() call happen later, when the ChromeTabbedActivity is visible. The logic is such that we do it once both native init and window focus events have been received. BUG=673831 Review-Url: https://codereview.chromium.org/2613573003 ==========
Message was sent while issue was closed.
Committed patchset #2 (id:40001)
Message was sent while issue was closed.
Description was changed from ========== Fix blank NTP bug on Clank. This was a result of the FRE refactor work for first run experiments, which had moved FirstRunActivity creation to be before native init. As a result of that, the removeBackground() ChromeTabbedActivity ended up happening when the activity was not foreground, which apparently caused the bug. This change fixes it by making the removeBackground() call happen later, when the ChromeTabbedActivity is visible. The logic is such that we do it once both native init and window focus events have been received. BUG=673831 Review-Url: https://codereview.chromium.org/2613573003 ========== to ========== Fix blank NTP bug on Clank. This was a result of the FRE refactor work for first run experiments, which had moved FirstRunActivity creation to be before native init. As a result of that, the removeBackground() ChromeTabbedActivity ended up happening when the activity was not foreground, which apparently caused the bug. This change fixes it by making the removeBackground() call happen later, when the ChromeTabbedActivity is visible. The logic is such that we do it once both native init and window focus events have been received. BUG=673831 Committed: https://crrev.com/928bfdc6404ea14bc71c28ef3e483453c34d0c52 Cr-Commit-Position: refs/heads/master@{#441378} ==========
Message was sent while issue was closed.
Patchset 2 (id:??) landed as https://crrev.com/928bfdc6404ea14bc71c28ef3e483453c34d0c52 Cr-Commit-Position: refs/heads/master@{#441378} |