Closed
Bug 708556
Opened 13 years ago
Closed 7 years ago
Use a nsISmsRequest object instead of using processId in WebSMS
Categories
(Core :: DOM: Core & HTML, defect)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
INVALID
People
(Reporter: mounir, Unassigned)
References
Details
Original comment from cjones is in bug 674725 comment 154. Important part is: I think all we needed to do was instead of passing around requestIds, pass around nsISmsRequest references (or something like that). So the workflow across processes might have looked something like, content process: var req = navigator.mozSms.send(...) create nsIDOMSmsRequest for |req|. nsIDOMSmsRequest implements nsISmsRequest nsISmsService.send(..., req) nsRemoteSmsService: create PSmsRequestChild actor under PSms that wraps |req|. chrome process: recv ctor for PSmsRequest. Create nsISmsRequest that wraps PSmsRequestParent. PSmsRequestParent implements nsISmsRequest. nsISmsService.send(..., req) ...
Updated•7 years ago
|
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INVALID
Assignee | ||
Updated•6 years ago
|
Component: DOM → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•