Closed Bug 1485136 Opened 7 years ago Closed 7 years ago

Discuss and design HCT error handling

Categories

(Toolkit :: Telemetry, enhancement, P1)

Product:
Toolkit
Component:
Telemetry
Type:
enhancement
Points:
1

Tracking

()

Status:
RESOLVED FIXED
Tracking Flags:
Tracking Status
firefox63 --- affected

People

(Reporter: chutten, Assigned: chutten)

References

Details

Alessio and I should have a chat about HCT error handling. What comes out of that discussion should be enough shared information to proceed with a design or to close out bug 1476349 as something we've decided not to do.
We had a discussion today. The core decision is that, yes, if registerEvents throws we can certainly relay that back to the content. We talked a little bit about how we'd implement it with today's broadcast-based message approach (using message ids to correlate it with the correct call), and noted that we'd need Security Review (and that maybe Security knows a better "talk to the chrome" mechanism than broadcast that may have been implemented recently). I'll take these notes back to bug 1476349 and push it back out for Triage and prioritization with other current work.
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.