This decision is potentially very big. How can Chrome, a browser that has so actively pushed HTML5 forward, reject a component of the spec? I mean IE supports W

This decision is potentially very big. How can Chrome, a browser that has so actively pushed HTML5 forward, reject a component of the spec? I mean IE supports WebGL for crying out loud, I wasn't sure they ever would, but even they're playing ball. We'll see what happens here, its a pretty vague comment right now. What does "at this time" really mean? Is it just delayed so other things can be focused on? I could understand that. Things like the new input controls should be a bigger priority, they are more important for 99% of all users. Very interesting, it makes it hard for Chrome to criticize any other implementation.