- From: David Burns <dburns@mozilla.com>
- Date: Thu, 02 Oct 2014 15:11:02 +0100
- To: public-browser-tools-testing <public-browser-tools-testing@w3.org>
Hi All, I would like to propose that in Section 4.1 we remove desiredCapabilites and requiredCapabilites and just have a capabilities object. This capabilities object would then be treated as a requiredCapabilities object and if any of keys in that object do not match what the UA/intermediary node can do then error with a `session not created` status. If keys have been omitted from the capabilities object then the UA/intermediary node can just assume that the developer is happy with whatever they receive Currently I can't think of a use case where a developer would send through capabilities and only want a small subset. In Bug 26391[1] a use case has been put forward to making Proxy a required capability. By setting capabilities to always required it will simplify implementations and all developers to maintain a certain amount of determinism for their automation. It also would stop people asking for IE on Linux and getting Firefox which is what the current open source project does. I look forward to your feedback. David [1] https://www.w3.org/Bugs/Public/show_bug.cgi?id=26391
Received on Thursday, 2 October 2014 14:11:30 UTC