3 ms·
In this case, the intent degrades to a link to the action URI for browsers that don't support intents. What would be at the action URI? An error message or some
by extension 15y ago
In this case, the intent degrades to a link to the action URI for browsers that don't support intents. What would be at the action URI? An error message or something that tries to fulfill the intent?
- masklinn 15y ago> In this case, the intent degrades to a link to the action URI for browsers that don't support intents. Or when no support library is added on the client to provide some kind of in-page UI enhancement. Yes, that's the whole point: building on existing and well-functioning technologies to avoid that things break down completely and that a segment of the population is entirely left out for no good reason. > What would be at the action URI? An error message or something that tries to fulfill the intent? Second case, some sort of intents picker if multiple web services can fulfill it, or a redirection to the intent handler if there is only one. An error message if there is no registered service able to handle the intent. And it keeps the distribution of intents registrar from your proposal, which I think is a good idea.