Closed Bug 1069177 Opened 9 years ago Closed 9 years ago

B2G NFC: rename nsINfcPeerEventListener to nsINfcDOMEventTarget

Categories

(Firefox OS Graveyard :: NFC, defect)

Product:
Firefox OS Graveyard
Component:
NFC
Platform:
ARM
Gonk (Firefox OS)
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED
Milestone:
2.1 S6 (10oct)

People

(Reporter: allstars.chh, Assigned: allstars.chh)

References

Details

(Whiteboard: [p=2])

Attachments

(1 file, 1 obsolete file)

Patch.
14.52 KB, patch
dimi
: review+
Details | Diff | Splinter Review 
To implement ontagfound (Bug 991970) /onpeerfound (Bug 1003268),
we need to know the current foreground app and dispatch NFC event only to that app.

And those two bugs above the implementation is done in Parent process to keep track the current foreground app.

I'd propose another way to do this check in Child process.
Attached patch WIP. Patch. (obsolete) — — Splinter Review 
Assignee: nobody → allstars.chh

    
    

    
  
We're still discussing how to dispatch event to 'foreground' app with System app devs and Browser API devs.

So I'll do the rename part first in this bug.
Summary: B2G NFC: Dispatch NFC DOM Event to foreground app. → B2G NFC: rename nsINfcPeerEventListener to nsINfcDOMEventTarget

    
    

    
  

      
      
      
      

        Attached patch
          
          
        Patch.
        — 
          — Splinter Review
      

    


  

        Attachment #8491320 -
        Attachment is obsolete: true

        Attachment #8495760 -
        Flags: review?(dlee)

    
    

    
  
Comment on attachment 8495760 [details] [diff] [review]
Patch.

Review of attachment 8495760 [details] [diff] [review]:
-----------------------------------------------------------------

Looks good, thanks

        Attachment #8495760 -
        Flags: review?(dlee) → review+

    
    

    
  
https://hg.mozilla.org/mozilla-central/rev/99be50ec39a5
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED

          You need to log in
          before you can comment on or make changes to this bug.