On 2/25/06, Bret Pettichord <[EMAIL PROTECTED]> wrote: > It would be easy to extend Watir to support these input images with, say, > ie.image_button(blah) or ie.image_input(blah) in addition to the existing > support in ie.button(blah). I'm thinking making this a separate type would > key users that there were two types of images and that they had to use the > right type with Wat[i]r.
FWIW, I had exactly this misunderstanding and spent an hour or so trying to figure out why Watir wouldn't click the image. Then I realized precisely what Bret said about the term "image" being overloaded in HTML, tried button, and all was well. One advantage of having an alias image_button is that a search on the doc for /image/ (e.g., bringing the RDoc up in the browser and searching on my best guess at the appropriate method name) would match image_button. So I'd cast my vote for that simple solution. If making image.click work for input images wouldn't cause complications then so much the better, but just having a documented method image_button would probably prevent a "gotcha" for a few of us poor souls. JMO. Thanks, Philip _______________________________________________ Wtr-general mailing list [email protected] http://rubyforge.org/mailman/listinfo/wtr-general
