Re: [wtr-general] Re: unable to click image in a div

2010-07-22 Thread Basim Baassiri
I found a solution to my problem that I thought might useful to others When the underlying web application uses gwt ( http://code.google.com/webtoolkit/) , firing a sequence of mouse events can also get the desired click event fire_event onmouseover fire_event onmousedown fire_event onmouseup On

[wtr-general] Re: unable to click image in a div

2010-07-14 Thread Super Kevy
Consider autoit sendkeys. This is code (partial) scraped from the demo on the thumbs popup div class=product-panel-inner style=overflow: hidden; position: relative; div class=product-panel-title style=overflow: hidden; position: relative; div class=gwt-HTMLOVERSIZED SQUARE SUNGLASSES WITH

Re: [wtr-general] Re: unable to click image in a div

2010-07-14 Thread Basim Baassiri
Thanks Super for the suggestion.I was looking for a cross platform solution I tried you suggestion and it works (as a workaround) Thanks Basim On Wed, Jul 14, 2010 at 10:39 AM, Super Kevy kpe...@scholarshipamerica.orgwrote: Consider autoit sendkeys. This is code (partial) scraped from the

[wtr-general] Re: unable to click image in a div

2010-07-13 Thread orde
Did you try just browser.image(:class, gwt-Image).click or browser.image(:class, gwt-Image).fire_event(onload)? orde On Jul 13, 12:59 pm, Basim Baassiri ba...@baassiri.ca wrote: pre-conditions: ruby -v ruby 1.8.6 (2007-09-24 patchlevel 111) [i386-mswin32] gem list watir *** LOCAL GEMS ***

Re: [wtr-general] Re: unable to click image in a div

2010-07-13 Thread Basim Baassiri
orde, I tried your suggestion with no luck Basim On Tue, Jul 13, 2010 at 4:27 PM, orde ohil...@gmail.com wrote: Did you try just browser.image(:class, gwt-Image).click or browser.image(:class, gwt-Image).fire_event(onload)? orde On Jul 13, 12:59 pm, Basim Baassiri ba...@baassiri.ca wrote:

[wtr-general] Re: unable to click image in a div

2010-07-13 Thread Chuck van der Linden
Look in the HTML or scripting and see what events the div is set to respond to. Does it take on a different appearance when you mouseover it? it might be that the mouseover replaces the 'button-up' with something else (a 'button-focused' or 'button-active or somesuch, and it's actually that