[Bug 29168] New: Does it make sense to require the use of "unknown error"?

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

            Bug ID: 29168
           Summary: Does it make sense to require the use of "unknown
                    error"?
           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: juangj@gmail.com
        QA Contact: public-browser-tools-testing@w3.org
                CC: mike@w3.org
            Blocks: 20860
  Target Milestone: ---

>From 8. Invalid SSL Certificates:

"In this case, implementations may choose to make accessing a site with bad
HTTPS configurations cause a WebDriverException to be thrown. Remote end
implementations must return an unknown error error code in this case."

It seems odd to say that the remote end MUST return an "unknown error" in a
case where we know exactly what the error is. There doesn't seem to be any
other fitting error code, though.

Is "unknown error" intended to just be the catch-all for errors that don't fit
any of the other error codes?


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 Friday, 2 October 2015 06:46:27 UTC