[NTP Client] Do not refresh Tiles while visible
Tiles are now refreshed when:
- The TileGroup first receives data
- The user explicitly modifies the tiles (removes one)
- The user switches to an existing NTP or opens Home
Known issues:
- New NTPs might have stale data because on registration
it pulls the currently cached tile data, then refreshes it
expecting the NTP to display the changes. But this patches
explicitly blocks that.
BUG=694262
Review-Url: https://codereview.chromium.org/2742433002
Cr-Commit-Position: refs/heads/master@{#455806}
Committed: https://chromium.googlesource.com/chromium/src/+/2d368dbfe6323fe630398869d3e82c7d728a1035
Description was changed from ========== [NTP Client] Do not refresh Tiles while visible BUG= ========== ...
3 years, 9 months ago
(2017-03-08 17:27:24 UTC)
#1
Description was changed from
==========
[NTP Client] Do not refresh Tiles while visible
BUG=
==========
to
==========
[NTP Client] Do not refresh Tiles while visible
Tiles are now refreshed when:
- The TileGroup first receives data
- The user explicitly modifies the tiles (removes one)
- The user switches to an existing NTP or opens Home
Known issues:
- New NTPs might have stale data because on registration
it pulls the currently cached tile data, then refreshes it
expecting the NTP to display the changes. But this patches
explicitly blocks that.
BUG=694262
==========
Dry run: Try jobs failed on following builders: linux_android_rel_ng on master.tryserver.chromium.android (JOB_FAILED, https://build.chromium.org/p/tryserver.chromium.android/builders/linux_android_rel_ng/builds/246627)
3 years, 9 months ago
(2017-03-08 19:27:21 UTC)
#8
PTAL. Meaningful change: I now always replace mTiles with the pending data, even if I ...
3 years, 9 months ago
(2017-03-09 12:12:36 UTC)
#11
PTAL. Meaningful change: I now always replace mTiles with the pending data, even
if I don't send a notification that data changed. This is so that I can clear
the pending data to acknowledge that we loaded it.
If the data did not change, the tiles themselves should not have significant
changes and since we don't keep references, it should not have any impact to the
current behaviour.
dgn
note: patchset 4 should be easier that 5 to review vs master
3 years, 9 months ago
(2017-03-09 12:14:34 UTC)
#12
note: patchset 4 should be easier that 5 to review vs master
dgn
The CQ bit was checked by dgn@chromium.org to run a CQ dry run
3 years, 9 months ago
(2017-03-09 12:14:46 UTC)
#13
Sry, still LGTM. One nit, but you could do that in a followup. https://codereview.chromium.org/2742433002/diff/80001/chrome/android/java/src/org/chromium/chrome/browser/suggestions/TileGroup.java File ...
3 years, 9 months ago
(2017-03-09 18:38:12 UTC)
#20
CQ is committing da patch. Bot data: {"patchset_id": 80001, "attempt_start_ts": 1489084481029590, "parent_rev": "870bce2d5e6ed3ba5d7b513b69d55fdb26efc2d6", "commit_rev": "2d368dbfe6323fe630398869d3e82c7d728a1035"}
3 years, 9 months ago
(2017-03-09 18:40:55 UTC)
#21
CQ is committing da patch.
Bot data: {"patchset_id": 80001, "attempt_start_ts": 1489084481029590,
"parent_rev": "870bce2d5e6ed3ba5d7b513b69d55fdb26efc2d6", "commit_rev":
"2d368dbfe6323fe630398869d3e82c7d728a1035"}
commit-bot: I haz the power
Description was changed from ========== [NTP Client] Do not refresh Tiles while visible Tiles are ...
3 years, 9 months ago
(2017-03-09 18:41:33 UTC)
#22
Message was sent while issue was closed.
Description was changed from
==========
[NTP Client] Do not refresh Tiles while visible
Tiles are now refreshed when:
- The TileGroup first receives data
- The user explicitly modifies the tiles (removes one)
- The user switches to an existing NTP or opens Home
Known issues:
- New NTPs might have stale data because on registration
it pulls the currently cached tile data, then refreshes it
expecting the NTP to display the changes. But this patches
explicitly blocks that.
BUG=694262
==========
to
==========
[NTP Client] Do not refresh Tiles while visible
Tiles are now refreshed when:
- The TileGroup first receives data
- The user explicitly modifies the tiles (removes one)
- The user switches to an existing NTP or opens Home
Known issues:
- New NTPs might have stale data because on registration
it pulls the currently cached tile data, then refreshes it
expecting the NTP to display the changes. But this patches
explicitly blocks that.
BUG=694262
Review-Url: https://codereview.chromium.org/2742433002
Cr-Commit-Position: refs/heads/master@{#455806}
Committed:
https://chromium.googlesource.com/chromium/src/+/2d368dbfe6323fe630398869d3e8...
==========
commit-bot: I haz the power
Committed patchset #5 (id:80001) as https://chromium.googlesource.com/chromium/src/+/2d368dbfe6323fe630398869d3e82c7d728a1035
3 years, 9 months ago
(2017-03-09 18:41:34 UTC)
#23
Issue 2742433002: 📰 Do not refresh Tiles while visible
(Closed)
Created 3 years, 9 months ago by dgn
Modified 3 years, 9 months ago
Reviewers: Bernhard Bauer, fhorschig
Base URL:
Comments: 1