Re: [w3ctag/design-reviews] More restrictive hasEnrolledInstrument() for autofill data (#407)

The TAG is unsure about whether TAG review is needed for an implementation change that doesn't require spec changes.  If it's an issue that isn't important enough for the spec to specify clearly, then it's not clear why the TAG should be reviewing it.

That said, this does bring up the question of perhaps whether this should be specified in more detail in the spec.  Given the expectations that Chrome is setting, are other implementations of this API going to have to do the same thing in order to be compatible with the expectations of the API's users?  If so, then it might actually need to be in the spec.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/407#issuecomment-523301769