Actually enable tab persistence for CCTs.
TEST=Actually use the feature.
Turn on "Don't keep activities", leave a CCT, click on
it from recents. See that your final page is visible.
BUG=606513
Committed: https://crrev.com/426df5c8550a7a7a9623240bd46ba054817a7572
Cr-Commit-Position: refs/heads/master@{#418727}
4 years, 3 months ago
(2016-09-14 00:27:02 UTC)
#2
PTAL
Yusuf
https://codereview.chromium.org/2336413002/diff/1/chrome/android/java/src/org/chromium/chrome/browser/customtabs/CustomTabActivity.java File chrome/android/java/src/org/chromium/chrome/browser/customtabs/CustomTabActivity.java (right): https://codereview.chromium.org/2336413002/diff/1/chrome/android/java/src/org/chromium/chrome/browser/customtabs/CustomTabActivity.java#newcode311 chrome/android/java/src/org/chromium/chrome/browser/customtabs/CustomTabActivity.java:311: assert mMainTab == null; if we have run warmup ...
4 years, 3 months ago
(2016-09-14 18:20:51 UTC)
#3
https://codereview.chromium.org/2336413002/diff/1/chrome/android/java/src/org...
File
chrome/android/java/src/org/chromium/chrome/browser/customtabs/CustomTabActivity.java
(right):
https://codereview.chromium.org/2336413002/diff/1/chrome/android/java/src/org...
chrome/android/java/src/org/chromium/chrome/browser/customtabs/CustomTabActivity.java:311:
assert mMainTab == null;
if we have run warmup and early tab initialization, we will actually have
mMainTab non null at this point with it already loading the url that was in the
intent.
Maybe we should move this to createMainTab as an early intervention there? That
way both finishNativeInitialization and preInflationStartup calls would get it.
https://codereview.chromium.org/2336413002/diff/1/chrome/android/java/src/org...
chrome/android/java/src/org/chromium/chrome/browser/customtabs/CustomTabActivity.java:626:
mIsClosing = true;
I wonder if we can just use isDestroyed here? Are we worried about onDestroy
calling time and finish calling time not playing nice with each other?
Ted C
https://codereview.chromium.org/2336413002/diff/1/chrome/android/java/src/org/chromium/chrome/browser/customtabs/CustomTabActivity.java File chrome/android/java/src/org/chromium/chrome/browser/customtabs/CustomTabActivity.java (right): https://codereview.chromium.org/2336413002/diff/1/chrome/android/java/src/org/chromium/chrome/browser/customtabs/CustomTabActivity.java#newcode311 chrome/android/java/src/org/chromium/chrome/browser/customtabs/CustomTabActivity.java:311: assert mMainTab == null; On 2016/09/14 18:20:51, Yusuf wrote: ...
4 years, 3 months ago
(2016-09-14 20:29:12 UTC)
#4
https://codereview.chromium.org/2336413002/diff/1/chrome/android/java/src/org...
File
chrome/android/java/src/org/chromium/chrome/browser/customtabs/CustomTabActivity.java
(right):
https://codereview.chromium.org/2336413002/diff/1/chrome/android/java/src/org...
chrome/android/java/src/org/chromium/chrome/browser/customtabs/CustomTabActivity.java:311:
assert mMainTab == null;
On 2016/09/14 18:20:51, Yusuf wrote:
> if we have run warmup and early tab initialization, we will actually have
> mMainTab non null at this point with it already loading the url that was in
the
> intent.
>
> Maybe we should move this to createMainTab as an early intervention there?
That
> way both finishNativeInitialization and preInflationStartup calls would get
it.
Per the offline discussion, I think it is better to not create a tab early if we
are restoring state. Since you're refocusing from recents, it is very unlikely
that the warmup will be caused by the underlying app, so I don't think it's
worth the complexity to support it.
https://codereview.chromium.org/2336413002/diff/1/chrome/android/java/src/org...
chrome/android/java/src/org/chromium/chrome/browser/customtabs/CustomTabActivity.java:626:
mIsClosing = true;
On 2016/09/14 18:20:51, Yusuf wrote:
> I wonder if we can just use isDestroyed here? Are we worried about onDestroy
> calling time and finish calling time not playing nice with each other?
We wouldn't be destroyed at this point, so I think we need to track this
separately.
Yusuf
lgtm
4 years, 3 months ago
(2016-09-14 21:10:13 UTC)
#5
lgtm
gone
lgtm
4 years, 3 months ago
(2016-09-14 23:22:40 UTC)
#6
lgtm
Ted C
The CQ bit was checked by tedchoc@chromium.org
4 years, 3 months ago
(2016-09-15 00:04:02 UTC)
#7
4 years, 3 months ago
(2016-09-15 00:38:23 UTC)
#10
Message was sent while issue was closed.
Committed patchset #3 (id:40001)
commit-bot: I haz the power
Description was changed from ========== Actually enable tab persistence for CCTs. TEST=Actually use the feature. ...
4 years, 3 months ago
(2016-09-15 00:40:14 UTC)
#11
Message was sent while issue was closed.
Description was changed from
==========
Actually enable tab persistence for CCTs.
TEST=Actually use the feature.
Turn on "Don't keep activities", leave a CCT, click on
it from recents. See that your final page is visible.
BUG=606513
==========
to
==========
Actually enable tab persistence for CCTs.
TEST=Actually use the feature.
Turn on "Don't keep activities", leave a CCT, click on
it from recents. See that your final page is visible.
BUG=606513
Committed: https://crrev.com/426df5c8550a7a7a9623240bd46ba054817a7572
Cr-Commit-Position: refs/heads/master@{#418727}
==========
commit-bot: I haz the power
Patchset 3 (id:??) landed as https://crrev.com/426df5c8550a7a7a9623240bd46ba054817a7572 Cr-Commit-Position: refs/heads/master@{#418727}
4 years, 3 months ago
(2016-09-15 00:40:15 UTC)
#12
Issue 2336413002: Actually enable tab persistence for CCTs.
(Closed)
Created 4 years, 3 months ago by Ted C
Modified 4 years, 3 months ago
Reviewers: gone, Yusuf
Base URL:
Comments: 4