Closed Bug 917466 Opened 11 years ago Closed 7 years ago

Investigate crash queing

Categories

(Firefox for Metro Graveyard :: General, defect)

Product:
Firefox for Metro Graveyard
Component:
General
Platform:
x86_64
Windows 8.1
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED INCOMPLETE

People

(Reporter: jimm, Unassigned)

References

Details

(Whiteboard: [feature] p=0)

Supposedly we have the ability now through B2G work to queue crash reports and send them when we get started up and know we have connection. Filing this to investigate. http://mxr.mozilla.org/mozilla-central/source/b2g/chrome/content/shell.js#108 http://mxr.mozilla.org/mozilla-central/source/browser/metro/base/content/browser-ui.js#248
Whiteboard: [preview-triage]
block preview?
Flags: needinfo?(asa)
How hard would this be to get? What do we think about our current solution for v1? Is it enough? Is this a must have? If not, my leaning is to punt to v2.
Flags: needinfo?(asa)
Blocks: metrobacklog
No longer blocks: metrov1backlog
Whiteboard: [preview-triage]
Whiteboard: [feature]
Whiteboard: [feature] → [feature] p=0
OS: Windows 8 Metro → Windows 8.1
Mass close of bugs in obsolete product https://bugzilla.mozilla.org/show_bug.cgi?id=1350354
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.