Skip to content
This repository was archived by the owner on Nov 29, 2018. It is now read-only.
This repository was archived by the owner on Nov 29, 2018. It is now read-only.

EventFiringWebDriver should not be instantiable directly #2510

Open
@lukeis

Description

@lukeis

Originally reported on Google Code with ID 2510

A "new EventFiringWebDriver(...)" statement is needed to use this class. This is not
in the spirit of WebDriver's API where the functionalities are split among interfaces.
The consequence is that a driver wrapped this way won't implement the same interfaces
than the wrapped one (see attached unit test).

The right solution to would be to prohibit direct instantiation and to use a dynamic
proxy like it is done for RemoteDriver in the Augmenter class.

Reported by [email protected] on 2011-09-21 07:08:21


- _Attachment: [patchTestEventFiringWebDriver.txt](https://storage.googleapis.com/google-code-attachments/selenium/issue-2510/comment-0/patchTestEventFiringWebDriver.txt)_

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions