It's a set of slides about HTML5 written in HTML5. The slides not working properly on mobile devices with no fallback for non-webkit browsers show that the developers are either
a. Lazy
b. Incompetent, or
c. Used proprietary webkit technology,
none of which will inspire much confidence in the actual contents of slides (which I can't read anyway, since I'm on Opera Mobile)
Any of the vast number of things that (1) WebKit implements but aren't in any standard or (2) Are in a standard but WebKit implements with a different name (sometimes in addition to the standard name).
first line of the deck clearly states, "If using Google Chrome, you will likely need the Dev channel to see all of the functionality in this presentation," which i take to mean, "if you're not using a fresh Chrome beta, this isn't going to work so well for you."
Comments
It's a set of slides about HTML5 written in HTML5. The slides not working properly on mobile devices with no fallback for non-webkit browsers show that the developers are either
a. Lazy b. Incompetent, or c. Used proprietary webkit technology,
none of which will inspire much confidence in the actual contents of slides (which I can't read anyway, since I'm on Opera Mobile)
What is proprietary webkit technology?
The ones which doesn't work in other standard-compliant browsers, like Firefox.
Any of the vast number of things that (1) WebKit implements but aren't in any standard or (2) Are in a standard but WebKit implements with a different name (sometimes in addition to the standard name).
first line of the deck clearly states, "If using Google Chrome, you will likely need the Dev channel to see all of the functionality in this presentation," which i take to mean, "if you're not using a fresh Chrome beta, this isn't going to work so well for you."