Re: [sensors] Introduce WebDriver extension API

Hi @Honry! I'm a little confused about this latest change. Why does a "mock
sensor" need both a "mock sensor reading" and a "default mock sensor reading"?
Perhaps if we needed to reset the mock sensor reading to the initial value, the
"default mock sensor reading" would be a useful piece of information to
maintain. I don't think we need this, though. As written, the "update mock
sensor reading" algorithm suggests that the "default mock sensor reading"
should be modified. At that point, is it really still the "default"?

As I understood the previous iteration, the initial value of the "mock sensor
reading" was selected by the UA, and the WebDriver extension commands allowed
developers to modify that value directly. Is that right? Is there some aspect
of that architecture which caused problems?

GitHub Notification of comment by jugglinmike
Please view or discuss this issue at using your GitHub account

Received on Wednesday, 29 August 2018 20:33:42 UTC