[Bug 29524] New: Processing capabilities algorithm sort of half-defines the behaviour of intermediary nodes

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

            Bug ID: 29524
           Summary: Processing capabilities algorithm sort of half-defines
                    the behaviour of intermediary nodes
           Product: Browser Test/Tools WG
           Version: unspecified
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: WebDriver
          Assignee: public-browser-tools-testing@w3.org
          Reporter: james@hoppipolla.co.uk
        QA Contact: public-browser-tools-testing@w3.org
                CC: mike@w3.org
            Blocks: 20860
  Target Milestone: ---

For a browser "remote end", I think all of the Processing Capabilities steps
are irrelevant except perhaps for reading "acceptSslCerts", "proxy" and
"pageLoadStrategy" and configuring the browser as required to set those. For an
intermediary node which acts as a interface to many possible remote ends there
are presumably semantic requirements on the other listed properties, but the
spec doesn't really set those out and has strangeness like a vestigial "unmet
capabilities" variable that is initialized but never modified.


Referenced Bugs:

https://www.w3.org/Bugs/Public/show_bug.cgi?id=20860
[Bug 20860] WebDriver Level 1
-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Wednesday, 9 March 2016 21:37:22 UTC