Closed Bug 1126653 Opened 6 years ago Closed 6 years ago
don't send nfc-manager-tech-lost if the foreground has received ontag/peerfound
This is a follow-up in Bug 1082443. In Bug 1082443 we broadcast nfc-manager-tech-discovered when app cannot handle this. But if the app could handle the event, when the tag/peer is removed, we still send nfc-manager-tech-lost to System app, which is inconsistent. We should also prevent sending nfc-manager-tech-lost if the app has received ontag/peerfound before.
6 years ago
Attachment #8555650 - Flags: review?(dlee)
Target Milestone: --- → 2.2 S5 (6feb)
Comment on attachment 8555650 [details] [diff] [review] Patch. v2 NOTE: Please see https://wiki.mozilla.org/Release_Management/B2G_Landing to better understand the B2G approval process and landings. [Approval Request Comment] Bug caused by (feature/regressing bug #): Bug 1082443 User impact if declined: Phone will still vibrate even the foreground app has processed NFC event. Testing completed: Manually. Risk to taking this patch (and alternatives if risky): No. String or UUID changes made by this patch: Update uuid in nsINfcContentHelper.idl, which is an internal IDL.
Attachment #8555650 - Flags: approval-mozilla-b2g37?
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Attachment #8555650 - Flags: approval-mozilla-b2g37? → approval-mozilla-b2g37+
You need to log in before you can comment on or make changes to this bug.