Refactor ChromeDriver::setValue
Looking at ChromeDriver::setValue
and ChromeDriver::setNonTextTypeValue
I think we should split setValue
into setValue
(decide which method) and ChromeDriver::setTextTypeValue
(if not setNonTextTypeValue
).
That would make changes like !112 (closed) clearer.
Edited by Chris Burgess