Hi!

I am trying to use Selenium to mark the position of elements in a screen shot taken
with Selenium. The steps I take are as follows:

- Start the Webdriver and navigate to a URL.
- Take a screen shot of the page.
- Use WebDriver.findElements to identify block level elements (divs) in the page.
- Use WebElement.getLocation and WebElement.getSize to get the area where each element
is located in the screen shot.
- Draw the corresponding rectangle at the extracted coordinates in the screen shot.

I'm trying this for IE, Firefox and Chrome. For some browsers, I get correctly sized
rectangles at a slightly different position, but the offset is constant. However, in
Chrome 13 on Windows for example the rectangles are to small and sometimes (and that's
really a problem) and the wrong position.

My question is: Is this a known problem? I searched the issue tracker and asked at
the mailing list, but didn't get a reply. It seems that the Webdriver uses Javascript
to get the coordinates, which may be a problem. What's really weird is that it sometimes
works and sometimes doesn't.

My setup is as follows:

Selenium version: 2.5.0
OS: Linux (Hub), Windows (Browser)
Browser: Chrome 
Brower version: 13

I use a RemoteWebDriver running on Linux to connect to a selenium server running on
Windows, which launches Chrome. 

To further investigate the problem, I am using Javascript to change the background
color of the divs I'm interested in and take a screen shot again. For some browsers,
there is a severe mismatch between the rectangle returned by getLocation and getSize
and the actual position where the element is rendered by the browser.

Maybe this has something to do with using screen shots and getLocation/getSize together?
I would settle for anything that gives me consistent (maybe offset) results for anything.

Thanks in advance for your help/comments.

Valentin

Please provide any additional information below. A sample reduced test
case, or a public URL that demonstrates the problem will intrigue our merry
band of Open Source developers far more than nothing at all: they'll be far
more likely to look at your problem if you make it easy for them!