[Bug 24974] New: The distinction between Capabilities and MutableCapabilities is not useful in the context of this spec

https://www.w3.org/Bugs/Public/show_bug.cgi?id=24974

            Bug ID: 24974
           Summary: The distinction between Capabilities and
                    MutableCapabilities is not useful in the context of
                    this spec
           Product: Browser Test/Tools WG
           Version: unspecified
          Hardware: All
               URL: https://dvcs.w3.org/hg/webdriver/raw-file/ac1cadc32661
                    /webdriver-spec.html#browser-capabilities
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: WebDriver
          Assignee: public-browser-tools-testing@w3.org
          Reporter: fisherii@google.com
        QA Contact: public-browser-tools-testing@w3.org
                CC: mike@w3.org
            Blocks: 20860

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 from Marc Fisher <fisherii@google.com> ---
*** Bug 24975 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Monday, 10 March 2014 17:49:24 UTC