Closed
Bug 933665
Opened 11 years ago
Closed 10 years ago
Remove encodeNdefRecords func from NfcContentHelper
Categories
(Firefox OS Graveyard :: NFC, defect)
Firefox OS Graveyard
NFC
Tracking
(firefox39 fixed)
RESOLVED
FIXED
2.2 S12 (15may)
Tracking | Status | |
---|---|---|
firefox39 | --- | fixed |
People
(Reporter: psiddh, Assigned: allstars.chh)
References
Details
(Whiteboard: [p=1])
Attachments
(1 file)
(deleted),
patch
|
dimi
:
review+
|
Details | Diff | Splinter Review |
User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/536.11 (KHTML, like Gecko) Ubuntu/12.04 Chromium/20.0.1132.47 Chrome/20.0.1132.47 Safari/536.11
Steps to reproduce:
This is a current limitation when a DOMString is used in sequences of Moz DOM Objects.
Strings such as 'type', 'id' 'payload' (of MozNdefRecord obj) will not be acccessible to NfcWorker.
Therefore as a workaround exists in the form of , wrapper intermediate function
Updated•11 years ago
|
Blocks: backlog-RIL/Net/Conn
Assignee | ||
Updated•11 years ago
|
Assignee: nobody → allstars.chh
Assignee | ||
Comment 1•11 years ago
|
||
It's because nsFrameMessageManager can't create structure clone of MozNDEFRecord.
Assignee: allstars.chh → nobody
Status: UNCONFIRMED → RESOLVED
Closed: 11 years ago
Resolution: --- → WONTFIX
Comment 2•11 years ago
|
||
This seems to be the same limitation sending a MozNDEFRecord from App to App via Activity. If so, I'll open a bug, unless that won't be implemented. Then we should consider sending a dictionary object across.
Assignee | ||
Comment 3•10 years ago
|
||
Given I have implemented Structured Clone for NDEF in Bug 1138886, I'll fix this once I also fix Bug 1139830.
Assignee: nobody → allstars.chh
Status: RESOLVED → REOPENED
Depends on: 1139830
Ever confirmed: true
Resolution: WONTFIX → ---
Assignee | ||
Comment 4•10 years ago
|
||
Assignee | ||
Updated•10 years ago
|
Attachment #8573187 -
Flags: review?(dlee)
Updated•10 years ago
|
Attachment #8573187 -
Flags: review?(dlee) → review+
Assignee | ||
Comment 5•10 years ago
|
||
Whiteboard: [p=1]
Target Milestone: --- → 2.2 S12 (15may)
Status: REOPENED → RESOLVED
Closed: 11 years ago → 10 years ago
status-firefox39:
--- → fixed
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•