Closed
Bug 1278644
Opened 8 years ago
Closed 8 years ago
Adapters behind History and TopSites home panels need stable getItemId implementations
Categories
(Firefox for Android Graveyard :: General, defect)
Firefox for Android Graveyard
General
Tracking
(firefox49 fixed, fennec+, firefox50 fixed)
RESOLVED
FIXED
Firefox 50
People
(Reporter: Grisha, Assigned: Grisha)
References
Details
Attachments
(4 files, 2 obsolete files)
58 bytes,
text/x-review-board-request
|
sebastian
:
review+
|
Details |
58 bytes,
text/x-review-board-request
|
sebastian
:
review+
|
Details |
58 bytes,
text/x-review-board-request
|
sebastian
:
review+
|
Details |
13.19 KB,
patch
|
Sylvestre
:
approval-mozilla-aurora+
|
Details | Diff | Splinter Review |
Similarly to Bug 1270068, icon/thumbs for websites blink multiple times when website is opened in a new tab.
Assignee | ||
Comment 1•8 years ago
|
||
One workaround might be to implement getItemId() and force hasStableIds(true) for both CombinedHistoryAdapter and ClientsAdapter. After some quick tests, this seems to help with recycling views. CombinedHistoryAdapter's getItemId is simple - we have either history_id or bookmark_id we can use. ClientsAdapter is a little trickier, since our underlying data there is a list of tuples (client_guid, tab_id).
Updated•8 years ago
|
tracking-fennec: --- → ?
tracking-fennec: ? → +
Comment 2•8 years ago
|
||
I'd really like to see this get fixed, this looks pretty janky. I also see this happen if your history is syncing while you're looking at the history panel. Maybe another good bug for Daniel?
Summary: Website icons blink multiple times in the History panel when websites are opened in a new tab → Website icons blink multiple times in the History panel when data set updates
Comment 3•8 years ago
|
||
(In reply to :Margaret Leibovic from comment #2) > I'd really like to see this get fixed, this looks pretty janky. I also see > this happen if your history is syncing while you're looking at the history > panel. > > Maybe another good bug for Daniel? Grisha, you mentioned this earlier, were you looking at this?
Flags: needinfo?(gkruglov)
Assignee | ||
Updated•8 years ago
|
Assignee: nobody → gkruglov
Status: NEW → ASSIGNED
Flags: needinfo?(gkruglov)
Assignee | ||
Comment 4•8 years ago
|
||
VisitedAdapter in TopSitesPanel has a related problem (results in blinking of icons on the top sites panel) - it's relying on default getItemId implementation, which returns value of the _id column, which in case of top sites data is always 0 (since it's backed by Combined view, and that's the sort of thing Combined view does). Going to address it in this ticket as well.
Assignee | ||
Updated•8 years ago
|
Summary: Website icons blink multiple times in the History panel when data set updates → Adapters behind History and TopSites home panels need stable getItemId implementations
Assignee | ||
Comment 5•8 years ago
|
||
Review commit: https://reviewboard.mozilla.org/r/61130/diff/#index_header See other reviews: https://reviewboard.mozilla.org/r/61130/
Attachment #8766110 -
Flags: review?(s.kaspari)
Attachment #8766111 -
Flags: review?(s.kaspari)
Attachment #8766112 -
Flags: review?(s.kaspari)
Assignee | ||
Comment 6•8 years ago
|
||
Review commit: https://reviewboard.mozilla.org/r/61132/diff/#index_header See other reviews: https://reviewboard.mozilla.org/r/61132/
Assignee | ||
Comment 7•8 years ago
|
||
Review commit: https://reviewboard.mozilla.org/r/61134/diff/#index_header See other reviews: https://reviewboard.mozilla.org/r/61134/
Updated•8 years ago
|
Attachment #8766110 -
Flags: review?(s.kaspari) → review+
Comment 8•8 years ago
|
||
Comment on attachment 8766110 [details] Bug 1278644 - Stable getItemId implementation for CombinedHistoryAdapter https://reviewboard.mozilla.org/r/61130/#review58380
Comment 9•8 years ago
|
||
Comment on attachment 8766111 [details] Bug 1278644 - Stable getItemId implementation for VisitedAdapter https://reviewboard.mozilla.org/r/61132/#review58382
Attachment #8766111 -
Flags: review?(s.kaspari) → review+
Comment 10•8 years ago
|
||
Comment on attachment 8766112 [details] Bug 1278644 - Stable getItemID implementation for ClientsAdapter https://reviewboard.mozilla.org/r/61134/#review58384
Attachment #8766112 -
Flags: review?(s.kaspari) → review+
Assignee | ||
Comment 11•8 years ago
|
||
https://hg.mozilla.org/integration/fx-team/rev/304c5fbd71618e5659d6d3b4c02537bca5d71625 Bug 1278644 - Stable getItemId implementation for CombinedHistoryAdapter r=sebastian https://hg.mozilla.org/integration/fx-team/rev/9e1003b7d84f0f83241d476e28fd8cfcdf43091f Bug 1278644 - Stable getItemId implementation for VisitedAdapter r=sebastian https://hg.mozilla.org/integration/fx-team/rev/24f4b4e4e22dd5ab16c411133100b31afa1d0cb1 Bug 1278644 - Stable getItemID implementation for ClientsAdapter r=sebastian
Assignee | ||
Comment 12•8 years ago
|
||
Note to self - this probably needs to be uplifted to 49.
Flags: needinfo?(gkruglov)
Comment 13•8 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/304c5fbd7161 https://hg.mozilla.org/mozilla-central/rev/9e1003b7d84f https://hg.mozilla.org/mozilla-central/rev/24f4b4e4e22d
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
status-firefox50:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → Firefox 50
Assignee | ||
Comment 14•8 years ago
|
||
Approval Request Comment [Feature/regressing bug #]: Generated favicons were introduced in Bug 1228680, which landed in 49. [User impact if declined]: When on Top Sites (interacting with items outside of the grid) or History panels (interacting with any history item), if user opens history a item in a background tab, they will see all visible generated favicons blink once or multiple times. [Describe test coverage new/current, TreeHerder]: Local testing. [Risks and why]: Seems low risk; some logic was added to generate stable IDs for three adapters behind these home panels; at worse, we might end up recycling views incorrectly, but we were already doing that. [String/UUID change made/needed]: none
Flags: needinfo?(gkruglov)
Attachment #8768677 -
Flags: approval-mozilla-aurora?
Comment 15•8 years ago
|
||
Comment on attachment 8768677 [details] [diff] [review] stable-ids-for-home-panels.patch Fix for favicon blinking, regression from 49. Let's try it in aurora.
Attachment #8768677 -
Flags: approval-mozilla-aurora? → approval-mozilla-aurora+
Comment 16•8 years ago
|
||
bugherder uplift |
https://hg.mozilla.org/releases/mozilla-aurora/rev/9ff2ed0592d8
status-firefox49:
--- → fixed
Comment 17•8 years ago
|
||
sorry backed out for bustage https://treeherder.mozilla.org/logviewer.html#?job_id=3008934&repo=mozilla-aurora
Flags: needinfo?(gkruglov)
Assignee | ||
Comment 18•8 years ago
|
||
Specific failure: https://treeherder.mozilla.org/logviewer.html#?job_id=3008934&repo=mozilla-aurora#L21417
Assignee | ||
Comment 19•8 years ago
|
||
Seems that I've missed a dependency on Bug 1251362. Specifically, this bit of code https://hg.mozilla.org/mozilla-central/rev/0c997d222636#l1.106 It should be trivial to create a patch which works around this conflict. However, I'm not clear as to what happens when Bug 1251362 hits aurora - the code in question will need to be modified again (to its present state). Carsten, could you please clarify how to proceed in this case? Thanks!
Flags: needinfo?(gkruglov) → needinfo?(cbook)
Comment 20•8 years ago
|
||
(In reply to :Grisha Kruglov from comment #19) > Seems that I've missed a dependency on Bug 1251362. Specifically, this bit > of code https://hg.mozilla.org/mozilla-central/rev/0c997d222636#l1.106 > > It should be trivial to create a patch which works around this conflict. > However, I'm not clear as to what happens when Bug 1251362 hits aurora - the > code in question will need to be modified again (to its present state). > Carsten, could you please clarify how to proceed in this case? Thanks! Sylvestre can you take a look at this, seems this will cause problems when we uplift this bug here and we have the general merge day.
Flags: needinfo?(cbook) → needinfo?(sledru)
Comment 21•8 years ago
|
||
I need more information to understand the situation. Could you explain a bit more? Thanks
Flags: needinfo?(sledru)
Comment 22•8 years ago
|
||
11:46 <~Tomcat|sheriffduty> Sylvestre: so for bug 1278644 i think the problem is that the developer can fix his bustage, but when this bug is uplifted to aurora and central moves to aurora this will cause again a bustage and would need a new fix again thats at least how i understand comment #19
Flags: needinfo?(sledru)
Comment 23•8 years ago
|
||
(In reply to :Grisha Kruglov from comment #19) > Seems that I've missed a dependency on Bug 1251362. Specifically, this bit > of code https://hg.mozilla.org/mozilla-central/rev/0c997d222636#l1.106 > > It should be trivial to create a patch which works around this conflict. > However, I'm not clear as to what happens when Bug 1251362 hits aurora - the > code in question will need to be modified again (to its present state). > Carsten, could you please clarify how to proceed in this case? Thanks! But bug 1251362 is not going to get uplifted, so what's the problem? On merge day the state of mozilla-central is becoming "Aurora" and this state already includes your changes as well as the ones from bug 1251362. Whatever you uplift to aurora now will then be beta and is not affected by this.
Comment 24•8 years ago
|
||
(In reply to Sebastian Kaspari (:sebastian) from comment #23) > (In reply to :Grisha Kruglov from comment #19) > > Seems that I've missed a dependency on Bug 1251362. Specifically, this bit > > of code https://hg.mozilla.org/mozilla-central/rev/0c997d222636#l1.106 > > > > It should be trivial to create a patch which works around this conflict. > > However, I'm not clear as to what happens when Bug 1251362 hits aurora - the > > code in question will need to be modified again (to its present state). > > Carsten, could you please clarify how to proceed in this case? Thanks! > > But bug 1251362 is not going to get uplifted, so what's the problem? > > On merge day the state of mozilla-central is becoming "Aurora" and this > state already includes your changes as well as the ones from bug 1251362. > Whatever you uplift to aurora now will then be beta and is not affected by > this. yeah than i guess its ok to uplift, we would need however a new patch because of the first one with the bustage
Assignee | ||
Comment 25•8 years ago
|
||
Ah, my mental model of how release channels & uplifts worked was slightly off, hence my confusion. Attached is an updated patch, which removes mention of RECENT_TABS (dependency on Bug 1251362) and builds on top of current aurora.
Attachment #8768677 -
Attachment is obsolete: true
Assignee | ||
Comment 27•8 years ago
|
||
Updated uplift patch with merge conflicts resolved. [Feature/regressing bug #]: Generated favicons were introduced in Bug 1228680, which landed in 49. [User impact if declined]: When on Top Sites (interacting with items outside of the grid) or History panels (interacting with any history item), if user opens history a item in a background tab, they will see all visible generated favicons blink once or multiple times. [Describe test coverage new/current, TreeHerder]: Local testing. [Risks and why]: Seems low risk; some logic was added to generate stable IDs for three adapters behind these home panels; at worse, we might end up recycling views incorrectly, but we were already doing that. [String/UUID change made/needed]: none
Attachment #8774385 -
Attachment is obsolete: true
Attachment #8774471 -
Flags: approval-mozilla-aurora?
Comment 28•8 years ago
|
||
Comment on attachment 8774471 [details] [diff] [review] stable-ids-aurora.patch Let's take it in aurora, thanks!
Attachment #8774471 -
Flags: approval-mozilla-aurora? → approval-mozilla-aurora+
Comment 29•8 years ago
|
||
bugherder uplift |
https://hg.mozilla.org/releases/mozilla-aurora/rev/e3d202c9c230 https://hg.mozilla.org/releases/mozilla-aurora/rev/db67e1188e8d
Updated•3 years ago
|
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•