On Wednesday, December 21, 2016 at 12:51:10 AM UTC+11, Eric Rescorla wrote: > I'm not really following this argument. Usually when a document has been > floating > around a long time but clearly has basic design issues and can't get > consensus, > even when a major vendor has implemented it, that's a sign that it > *shouldn't* > be standardized until those issues are resolved. That's not standards > fatigue, > it's the process working as designed.
The API addresses the use cases, but people here see those use cases as too basic because they don't represent average users (e.g., Boris' somewhat esoteric network setup). Most people have wifi at home, which is somewhat unmetered - and access to mobile data, which often costs more (but not always true). The API, though ".type", allows the user and app to have a conversation about that: "you want me to download stuff over mobile? Its might cost ya, but if you are ok with it...". > None of this seems to add up to a strong argument that this functionality > should be in Firefox Certainly things could be improved - but again, the API just addresses the basic use cases (i.e., the 80% case - that gives us parity with native apps). The web still can't do most of the things this API is actually needed for (e.g., enabling apps like audio books, magazine subscriptions, etc.) so it's not too much of a big deal right now that it's not available. However, if we do get better native integration in the platform (particularly as it relates to multimedia assets), then this will be needed (or people will just use Chrome, as it will provide better control over downloads on mobile - which will be sad). _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
