In latest editor's draft of Web Intents,
second example posts an intent with type="text/uri-list" and
third example declares it accepts type="text/uri-list;type=image/*" intent.
But, according to matching section,
text/uri-list;type=image/* doesn't match against text/uri-list,
so third example can't accept the intent from second example.
IMO, possible fix is
- changing "text/uri-list" to "text/uri-list;type=image/" in second example,
- or, changing the matching algorithm to handle parameter part of type attribute.
This was technically OK, but a bad example (the second "type" is really a mime type parameter, not another mime type). I've just removed it.