Closed
Bug 1525431
Opened 6 years ago
Closed 6 years ago
Link navigation for cards
Categories
(Firefox :: New Tab Page, defect, P1)
Firefox
New Tab Page
Tracking
()
RESOLVED
INVALID
Iteration:
67.1 - Jan 28 - Feb 10
People
(Reporter: andreio, Assigned: andreio)
References
Details
Investigate the difference between relying on href
s vs dispatching an action to main to open the link. The issue being that data collection might fail.
For context the current TopStories implementation goes with option B while the Pocket Newtab version is just using hrefs.
Assignee | ||
Updated•6 years ago
|
Flags: needinfo?(khudson)
Updated•6 years ago
|
Flags: needinfo?(khudson)
Updated•6 years ago
|
Assignee: nobody → andrei.br92
Iteration: --- → 67.1 - Jan 28 - Feb 10
Priority: -- → P1
Comment 1•6 years ago
|
||
[Tracking Requested - why for this release]:
status-firefox66:
--- → affected
tracking-firefox66:
--- → ?
status-firefox67:
--- → affected
Assignee | ||
Comment 2•6 years ago
|
||
tldr sync click event listeners are guaranteed to finish executing before browser navigation.
jdm: since the event can synchronously prevent navigation, by definition it is finished before the browser navigates away
jdm: any async operations started during the event have no such guarantee, however
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → INVALID
Updated•5 years ago
|
Component: Activity Streams: Newtab → New Tab Page
You need to log in
before you can comment on or make changes to this bug.
Description
•