Re: Intro & Project Status

Hi Mark,

On Mon, Sep 7, 2015 at 6:26 PM, Mark James <mrj@rbate.com> wrote:

>
> How would an Android device not displaying a webpage with an active
> Web-NFC watch respond to a Web NFC message with a URI payload? Would it
> behave the same as reading a tag and open the URI, ignoring the following
> Web NFC record that carries the Web NFC Id (sending URL), or would it get
> confused?
>
> And if there *is* an active watch, would the page always absorb any
> Web-NFC message, with no ability to instead trigger the normal device
> response to the payload?
>
>
Let's walk through a use case.
Suppose the user has a web page open and in focus, that uses Web NFC.
The user taps on a tag.

Depending on settings, the tag may go to the app that is open and in focus,
if that handles Web NFC.
Otherwise the native selection UI may be displayed, with one of the entries
being "browser - web page", and another being a native app.
Note that if the web page is not open or in focus, then it is not able to
handle NFC at all, and should not appear as a content handler for NFC.
Anyway let's assume that the page is open and in focus, but we still get
the selection UI.

[native app]
- If the user selects the native app to handle the (web) tag, then it will
get the whole Web NFC message, and it can decide what to do with the Web
NFC record, which is of external type, which apps tend to handle only if
they recognize it's theirs, and ignore it if the URN in the type doesn't
match with what they expect. Or, they can learn to use Web NFC tags after a
while, and know which origin has written the message. They can also write
Web NFC messages, faking an origin into a regular Web NFC record...

[web page]
- If the user selects the web page, then the user agent will get the NFC
message from the underlying platform, and only then watches can be applied.
This may be a strange user experience if there is a watch that ignores the
type of tag... so the user is switched to the page, where nothing happens
because the watch filter ignores the message. Perhaps an info bar could be
displayed, and if that is a requirement, then this should be in the spec.
If you see this an issue, create an issue.


> Is this where host card emulation support comes in, or is that unrelated?
>
>
To my understanding it is unrelated.
For any case, HCE would also work only with a web page open and in focus.

I hope I understood well the questions.

Best regards,
Zoltan