After reading a NFC tag with URL data, browser should be launched and then connect to that URL.

Garner, could you please to provide a patch of example for this bug?

Sure, I can post a patch. A few general steps for NFC tags before then: - Add nfc readonly or readwrite permissions to the app manifest. - Add activity declaration in manifest (so system has a app target nfc-technology-discovered), wide open URL filter. - Implement stub activity handler (so app can process the activity messages) (UI reaction to the above additions: See activity picker come up to choose the browser, if it's not the only target). Then: - Add URL handler code for the pre-parsed URI that comes with the message data. - Open Browser tab with that URI/URL.

Ken: the permssions and manifest already exist due to P2P implementation, however, perhaps the NFC Tag function code can be added to that file as well.

One more thing: The 8376533 patch uses the pre-parsed NDEF Record on the tag (or other device). Complete handling actually means reading the complete tag (that is, more than the first NDEF record), so there needs to be a readNDEF in there if the browser the browser for some reason expects more data. For simple NDEFs however, the pre-parsed one is the fastest way to handle NDEF messages. It takes a bit more time to do the readNDEF with the user holding the phone out.

^ Correction, the first NDEF Message (NDEFRecord array) is sent along with the Activity too, not all messages. This is the usual case, given common NFC tags are just 144 bytes or so.

Thanks for your great help, Yoshi.

r? to Alive for nfc_manager changes r? to Ben for updating the manifest of Browser.

Comment on attachment 8377451 [details] PullRequest r+me for the manifest change.

Thanks for the review, Ben and Alive. Tree is close, add checkin-needed.

Master: e3a8e318ec95bed0124ca331a5770a064fd83811