obviously the standards process moves slower than innovation on web technologies, but many of the things that iOS doesn't support are not yet standards. E.g. We

obviously the standards process moves slower than innovation on web technologies, but many of the things that iOS doesn't support are not yet standards. E.g. WebRtc, which Nexedi's link shows had an update to the draft in September, so clearly it is not yet stabilized. The legal basis for requiring compatibility seems much thinner for complying with working drafts (or a working group note, edited August 31, September 7, and September 15, in the case of the webm link). I mean, what level of compatibility should you have with a document that says: > Implementors who are not taking part in the discussions are likely to find the specification changing out from under them in incompatible ways.