> In fact, it could be that the test was successful and now Chrome is waiting on something else before it adds proper support. I would argue this is likely the

> In fact, it could be that the test was successful and now Chrome is waiting on something else before it adds proper support. I would argue this is likely the case. If Chrome deems that something is useful (to them, for some definition of useful), they just release it (and if this something was on a standards track, too bad, it's out now).