Closed
Bug 1152352
Opened 9 years ago
Closed 9 years ago
The click frequency cap on suggested tiles does not work with e10s
Categories
(Firefox :: New Tab Page, defect)
Firefox
New Tab Page
Tracking
()
RESOLVED
WORKSFORME
Tracking | Status | |
---|---|---|
e10s | m8+ | --- |
People
(Reporter: emtwo, Assigned: ursula)
References
Details
No description provided.
Reporter | ||
Comment 1•9 years ago
|
||
Clicking a suggested tile should make it no longer appear in the new tab set of tiles. The click does not register with e10s and the suggested tile continues to appear after it's clicked.
Depends on: 1140496
Updated•9 years ago
|
tracking-e10s:
--- → m8+
Assignee | ||
Updated•9 years ago
|
Assignee: nobody → ursulasarracini
Assignee | ||
Comment 2•9 years ago
|
||
This can't be reproduced when the newtab page isn't running in e10s, but when it does what it looks like is happening is that after the suggested link has been clicked and new links are fetched from the parent in order to refresh the grid for the next newtab, the suggested link hasn't been cleared and marked as a "history" link instead of a "suggested" link, so when the child requests new links it'll get the old set of links with the suggested one still in there
Assignee | ||
Comment 3•9 years ago
|
||
I can't reproduce this on currently Nightly, when about:newtab isn't running in e10s. Maybe something got fixed along the way...are you able to reproduce? It's still broken when about:newtab runs in e10s but the patch to fix this can be folded into the patch for Bug 1021654.
Flags: needinfo?(msamuel)
Reporter | ||
Comment 4•9 years ago
|
||
Yea this is just an e10s bug. I am fine with merging the fix for this bug into Bug 1021654
Flags: needinfo?(msamuel)
Comment 5•9 years ago
|
||
Out of sheer curiosity, how did you know this was going to be broken? This bug was filed 2015-04-08, which was before ursula started on porting about:newtab to e10s.
Flags: needinfo?(msamuel)
Reporter | ||
Comment 6•9 years ago
|
||
This bug is unrelated to porting about:newtab to e10s. The bug was appearing in the original about:newtab with e10s enabled.
Flags: needinfo?(msamuel)
Comment 7•9 years ago
|
||
Ah, okay, so to summarize: - This bug existed with e10s enabled on 2015-04-08 - Since that time, this bug has somehow been fixed - we no longer see its symptoms in Nightly with e10s enabled - The patch that makes about:newtab run remotely seems to re-open this bug, but ursula will be folding her patch in to fix it with those about:newtab patches. Is that correct? I'm just trying to make sure I understand correctly. :)
Flags: needinfo?(msamuel)
Reporter | ||
Comment 8•9 years ago
|
||
Ah ok, I didn't know it was fixed in current nightly. But in that case, that sounds about right. :)
Flags: needinfo?(msamuel)
Comment 9•9 years ago
|
||
Are you able to confirm that it's fixed in current Nightly? ursula and I are reasonably certain, but we wanted to be sure to check with you, as you filed the bug.
Flags: needinfo?(msamuel)
Reporter | ||
Comment 10•9 years ago
|
||
I've confirmed that I no longer see this bug in Nightly
Flags: needinfo?(msamuel)
Assignee | ||
Comment 11•9 years ago
|
||
I'll mark this as works for me and I'll put the fix for e10s bustage in the patch for Bug 1021654
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•