- From: Jeffrey Yasskin <notifications@github.com>
- Date: Tue, 01 May 2018 20:03:28 +0000 (UTC)
- To: w3c/permissions <permissions@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 1 May 2018 20:04:12 UTC
I'm not sure if I'm reading https://w3c.github.io/webdriver/#processing-model correctly, but I see: > Let parse result be the result of [[parsing as JSON](https://w3c.github.io/webdriver/#dfn-parsing-as-json) with request’s body as the argument. > ... > let parameters be parse result. > ... > running the remote end steps for command with an argument named url variables whose value is url variables and an additional argument named parameters whose value is parameters. So, I think we *do* start with a Javascript object that's the output of `JSON.parse()`, which it makes sense to use WebIDL on. I hope it's not observable if WebDriver implementations lacking a JS engine go directly from the string to the dictionary object. That said, whatwg/infra#159 makes some good points about this being the wrong semantics in some cases. I think I'd weakly vote for keeping the current text until that's resolved, and then switching to it. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/permissions/issues/174#issuecomment-385773786
Received on Tuesday, 1 May 2018 20:04:12 UTC