Note: There are a few cases of duplicates in user autocompletion which are being worked on.

Crash when accessing navigator.mozTelephony from chrome page

RESOLVED FIXED in mozilla12

Status

()

Core
DOM: Device Interfaces
--
critical
RESOLVED FIXED
6 years ago
6 years ago

People

(Reporter: philikon, Assigned: Ben Turner (not reading bugmail, use the needinfo flag!))

Tracking

({crash})

Trunk
mozilla12
crash
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

6 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.

Comment 2

6 years ago
Criticality and priority are two different things.
Created attachment 587316 [details] [diff] [review]
Patch, v1

This has r=sicking.
Assignee: nobody → bent.mozilla
Status: NEW → ASSIGNED
Attachment #587316 - Flags: review+
Created attachment 587842 [details] [diff] [review]
Patch, v2

We decided to allow chrome access always.
Attachment #587316 - Attachment is obsolete: true
Attachment #587842 - Flags: review?(jonas)
Attachment #587842 - Flags: review?(jonas) → review+
https://hg.mozilla.org/integration/mozilla-inbound/rev/4abbedf5b4ca
https://hg.mozilla.org/mozilla-central/rev/4abbedf5b4ca
Status: ASSIGNED → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla12
You need to log in before you can comment on or make changes to this bug.