> I think Apple didn't want to do it because it was remotely threatening to their iOS App Store and I wonder if some kind of anti-trust litigation may eventuall

> I think Apple didn't want to do it because it was remotely threatening to their iOS App Store and I wonder if some kind of anti-trust litigation may eventually expose their leadership around webkit like this What actually happened: Mozilla rejected it on security grounds, then Apple agreed with Mozilla. How are you blaming Apple for Google putting together a bad spec. that no other browser vendor can accept? This happens time and time again. Google publish a specification that is not acceptable, both Mozilla and Apple reject it on privacy or security grounds, Google ships it in Chrome anyway, then people like you complain about Apple being mean. Here is Mozilla’s position: https://github.com/mozilla/standards-positions/issues/154 https://github.com/mozilla/standards-positions/issues/154 Here is Apple’s position: https://github.com/WebKit/standards-positions/issues/28 https://github.com/WebKit/standards-positions/issues/28