Overlapping elements may trigger incorrect event

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Consider a page in a hybrid app in which DOM element B is positioned on top 
of some target DOM element A. Also, B is located at the centre of A on the 
screen.
2. Perform a click on the target element A.

What is the expected output? What do you see instead?
Robotium performs the click on B. The click is expected to trigger the click 
handler of A. Instead, one of four things occur (the first three of which lead 
to undesirable outcomes).

- B is a descendant of A and B has its own event handler: this causes B's event 
handler to get triggered (along with A), which is unexpected.
- B is not a descendant of A and B has its own event handler: this causes B's 
event handler to get triggered, but not A's, which is unexpected.
- B is not a descendant of A and B does not have its own event handler: this 
causes A's event handler to not get triggered at all, which is unexpected.
- B is a descendant of A and B does not have its own event handler: this causes 
A's event handler to get triggered, as expected.

What version of the product are you using? On what operating system?
Robotium 4.3, Mac OSX 10.8.5

Please provide any additional information below.

When clicking on a web element, Robotium seems to perform the click at the 
centre of that element (or at least, the centre of the visible portion of the 
element). Perhaps this was a design choice, but it does lead to some unexpected 
results as described above. It would be good if Robotium could find some way to 
execute the click on some *non-overlapping* portion of the element.

Original issue reported on code.google.com by focariz...@gmail.com on 6 Nov 2013 at 7:53

[GoogleCodeExporter]

Thanks for reporting this. Lets see what we can do.

Original comment by renasr...@gmail.com on 11 Nov 2013 at 5:50

• Changed state: Accepted

[GoogleCodeExporter]

We have prioritised to do other things instead of this as its a lot of work to 
fix. 

Original comment by renasr...@gmail.com on 6 Jan 2014 at 7:54

• Changed state: WontFix