Crash when accessing navigator.mozTelephony from chrome page

RESOLVED FIXED in mozilla12

Status

()

defect
--
critical
RESOLVED FIXED
7 years ago
7 years ago

People

(Reporter: philikon, Assigned: bent.mozilla)

Tracking

({crash})

Trunk
mozilla12
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment, 1 obsolete attachment)

Right now we crash in NS_NewTelephony() if the page accessing navigator.mozTelephony is a chrome page because document->NodePrincipal()->GetURI() returns a null URI (the principal is the system principal).

Updated

7 years ago
Severity: normal → critical
Keywords: crash
I wouldn't say there's anything critical about this since (a) navigator.mozTelephony is not part of any normal Firefox build and (b) B2G's Gaia UI doesn't use chrome at all.
Criticality and priority are two different things.
Posted patch Patch, v1 (obsolete) — Splinter Review
This has r=sicking.
Assignee: nobody → bent.mozilla
Status: NEW → ASSIGNED
Attachment #587316 - Flags: review+
Posted patch Patch, v2Splinter Review
We decided to allow chrome access always.
Attachment #587316 - Attachment is obsolete: true
Attachment #587842 - Flags: review?(jonas)
https://hg.mozilla.org/mozilla-central/rev/4abbedf5b4ca
Status: ASSIGNED → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla12
You need to log in before you can comment on or make changes to this bug.