Re: [sensors] initialize a sensor object: Explicitly require |options| to be a SensorOptions (#439)

I don't think we want to do that due to being future proof. In the future you might add things and its a different version of the SensorOptions dict, so code written for a newer browser, might start failing in an older browser, which would be bad.

I think that we just need to look for the presence of those members and check their types, e.g. frequency should be a number and not an object, or a boolean etc.

-- 
GitHub Notification of comment by kenchris
Please view or discuss this issue at https://github.com/w3c/sensors/pull/439#issuecomment-1253544322 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 21 September 2022 11:04:06 UTC