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 24063 - Don't mandate augmenting the the WebDriver interface
Summary: Don't mandate augmenting the the WebDriver interface
Status: RESOLVED INVALID
Alias: None
Product: Browser Test/Tools WG
Classification: Unclassified
Component: WebDriver (show other bugs)
Version: unspecified
Hardware: PC Linux
: P2 normal
Target Milestone: ---
Assignee: David Burns :automatedtester
QA Contact: Browser Testing and Tools WG
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 20860
  Show dependency tree / graph
 
Reported: 2013-12-11 17:04 UTC by Andreas Tolfsen
Modified: 2014-07-01 16:19 UTC (History)
4 users (show)

See Also:

Attachments

Description Andreas Tolfsen 2013-12-11 17:04:18 UTC 
The spec currently says:

    If this capability is supported, local end MUST add the
    TakesScreenshot interface to the WebDriver interface.

We shouldn't mandate that the WebDriver interface is augmented,
because it's perfectly legal to use a bare-bones RemoteWebDriver type
against a backend that has more capabilities.
Comment 1 David Burns :automatedtester 2014-02-25 19:27:42 UTC 
the MUST should be SHOULD
Comment 2 Marc Fisher 2014-03-10 18:00:11 UTC 
Is it even useful to talk about augmenting in this spec? It seems to me that this is a local-end detail that could be handled in a variety of ways depending on the language, and the augmenting pattern is pretty specific to the particulars of the Selenium Java local-end implementation.
Comment 3 Andreas Tolfsen 2014-07-01 16:19:35 UTC 
After careful reconsideration I think Marc is right here.  We should actually not talk about the local end at all because the spec is now remote end only.

The augmentation is a WebIDL thing only and doesn't imply how a particular language needs to implement an API for the spec.