I don't feel that we need to consider Goutte, Browserkit or Zombie here. This is really concerned with the subset of drivers which are capable of testing applications that rely on CSS for behaviour - for example using `:hover` to implement a drop-down menu.

**CSSDriverTest** is attempting to outline how 'CSS capable' drivers should handle interactions such as ***click*** when CSS might be a factor. Selenium 2 doesn't allow this and as a result an exception is throw (via php-webdriver), to the best of my knowledge the Selenium driver doesn't (+ Sahi as @aik099 suggests).

The way I see this working in practice.....if I've an application with CSS (for menus or more complicated UI), I'd need to know which drivers I can use to run my test/feature suite and what I can expect from the drivers' API, i.e. what will happen if my ***click*** fails?

If that seems realistic to you both then we should ensure these 3 drivers offer up the same API for interactions such as ***click*** - do you consider this a good enough reason for the tests to exist in the CSSDriverTest?