963527 - NFC: re-dispatch nfc-ndef-discovered mozActivity if app cannot handle it.

Status: RESOLVED INVALID

(Firefox OS Graveyard :: NFC, defect)

Description

[Yoshi Cheng-Hao Huang [:allstars.chh][:allstarschh][:yoshi]]

This is mentioned by Jonas and Junichi-san,

When nfc_manager in system app dispatches the 'nfc-ndef-discovered' MozActivity,
if there more than one app have registered this event before, an App Selector Menu would be pop up to let user decides which app he wants to launch.

However if the selected app cannot handle this nfc-ndef-discovered event, there would be no chance for user to 're-select' the app again, what user can do is just re-tap the tag again.

We should think the posibility if we can re-dispatch the event if the app itself cannot handle it correctly.

File this bug as Gecko bug for now.

Comment 1

[Garner Lee]

Aside from the UX question (the user is free to select the same app again), it should be possible as MozActivity is also currently a DOMRequest:

https://developer.mozilla.org/en-US/docs/Web/API/MozActivity

Comment 2

[Yoshi Cheng-Hao Huang [:allstars.chh][:allstarschh][:yoshi]]

CCing Alive(Gaia) and Juwei(UX).

Currently we'd like to let user takes the device and re-tap the tag again.

Junichi-san, do you have some examples that we need to dispatch the event again,
instead of letting user to move the device away and re-tap the tag?

Comment 3

[Juwei Huang[:juwei]]

Hopefully it is a really rare case, otherwise it would be no sense to show up an option that cannot be opened.
If it happened, it should act the same as other NFC error case: re-tap again.

Comment 4

[Junichi Hashimoto]

Re-tapping is OK. I don't think re-dispatching is required.

I'm just wondering how the user notice that he should tap again when a tag is not handled.
Does SystemApp shows the 'please re-tap' message? (is it possible in the current framework?)

Comment 5

[Yoshi Cheng-Hao Huang [:allstars.chh][:allstarschh][:yoshi]]

I think the error message should be showed by the app selected by user.

Let's ask Alive for what can System app do for us in this situation.

Comment 6

[(inactive after 6/18) Alive Kuo [:alive]]

If the tag is not handled correctly, it's app's responsibility to postError to system app.
I don't really care who displays the error message, app or system, but if app doesn't do anything, we (system) couldn't know the tag is handled well.

Comment 7

[Junichi Hashimoto]

If apps take the responsibility, reviews should ensure that apps treat tags correctly. 
Otherwise the user might encounter strange situations that nothing happen even if he taps many times.

Comment 8

[Juwei Huang[:juwei]]

Quick question: If the user already select an app to open the file and failed, is it possible to block certain app when the user try again? which means if one app fail to handle at the first time, it won't show on the selector menu next time.

Comment 9

[(inactive after 6/18) Alive Kuo [:alive]]

(In reply to Juwei Huang from comment #8)
> Quick question: If the user already select an app to open the file and
> failed, is it possible to block certain app when the user try again? which
> means if one app fail to handle at the first time, it won't show on the
> selector menu next time.

This is a general activity issue -- if you really think it's a problem.
For now OS cannot do things as to blame the app it declares it has the ability to deal with certain ability but actually it doesn't.

For core apps we provided I don't think we need to worry,
and for third party app let's be confident with the review of the marketplace.