This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 24975 - The distinction between Capabilities and MutableCapabilities is not useful in the context of this spec
Summary: The distinction between Capabilities and MutableCapabilities is not useful in...
Status: RESOLVED DUPLICATE of bug 24974
Alias: None
Product: Browser Test/Tools WG
Classification: Unclassified
Component: WebDriver (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Browser Testing and Tools WG
QA Contact: Browser Testing and Tools WG
URL: https://dvcs.w3.org/hg/webdriver/raw-...
Whiteboard:
Keywords:
Depends on:
Blocks: 20860
  Show dependency tree / graph
 
Reported: 2014-03-07 23:17 UTC by Marc Fisher
Modified: 2014-03-10 17:49 UTC (History)
1 user (show)

See Also:

Attachments

Description Marc Fisher 2014-03-07 23:17:32 UTC 
Capabilities vs. MutableCapabilities is a local-end distinction that could vary between different languages (e.g. if there were Haskell bindings, there would not be a MutableCapabilities, as mutability is not a supported concept in that language).

For this spec, I think we should just make it clear what exactly is meant by the capabilities object that are transferred by the wire protocol, e.g. how required and desired are used, and that capabilities returned by newSession describe the actual, unchangeable capabilities of that session.
Comment 1 Marc Fisher 2014-03-10 17:49:22 UTC 

*** This bug has been marked as a duplicate of bug 24974 ***