Paul Cotton <Paul.Cotton@microsoft.com>, 2015-07-06 19:41 +0000: > Archived-At: <http://www.w3.org/mid/BN3PR0301MB118535D834D4DD5A67AF3CB2EA930@BN3PR0301MB1185.namprd03.prod.outlook.com> > > > Many of the *Track interface pieces are yet to be implemented in Chrome, > > Are these currently interfaces implemented in any other MSE implementations? I believe they are not supported in an UAs at all yet. Certainly we don’t have two UAs that support them. Given that, it’s not clear to me why they weren’t listed as “at risk” in the CR publication. We’re definitely not going to be transition the spec out of CR if we can’t document that we have at least two implementations of those features (and we actually don’t even have tests for those features themselves yet—all we have at this point is just the simple test that checks whether the interface exposes members for them as expected). One option of course is to drop them from the spec (and move them to a v2) and take just the sets of features to Rec for which we can demonstrate that we have at least two implementations. —Mike -- Michael[tm] Smith https://people.w3.org/mike
Received on Wednesday, 8 July 2015 12:30:34 UTC