Map report is offset ~50 px to the right

The heatmap is rendered on top of an actually page rendering in the browser. That means that the clicks are scaled and are not a 100% accurate. I have some ideas for fixing this, but that is the way the library is intended to work.

Basically it records the x, y location of the click on the screen. That means that if you click when the browser is 800x600 and the site layout is scaled to fit that the menus may be in a different location when viewed at larger resolutions. The click heatmap is a transparent image scaled to your viewing resolution and is placed over a iframe rendering the actually page using the browser. That means the page layout is scaled to fit in that window.

Try using the admin tools provided by the library instead of viewing through the Drupal interface. At some point when I get some time I will try and provide a work around for this problem. One solution may be to rewrite this with the UTS framework.

My laptop's resolution is 1280x800, and my clicks show up perfectly when the log is viewed as 1280 wide. However, what does this mean for users with 800x600 or 1024x768?

Would a suitable fix be... calculating the X and Y percentage instead of pixel? Example... On a 1024 display, someone clicks 200 pixels from the left, so it would be 19.5% on 1024. Would it be accurate to adjust on a 1280 to say that it would be equivalent to 249.6 pixels from the left?

I didn't write the actually library that records and renders the clicks. My modules just integrates it with Drupal. To my understanding it tries to scale the click locations, but the problem is that it renders the webpage at the resolution it is displaying. The menu may scale unevenly compared to pixel locations.

I am going to write a pure Drupal implementation of this for UTS in the near future which would hopefully overcome this problem in some manor.

If you can figure out a patch for this module in the meantime that would be great, but I don't have time at the moment, especially since I didn't write the library. I believe if you tell it what resolution to render at it will only get clicks from that resolution which may be one solution.

hi,

Have similar results - for example, if I open page in Firefox in full window (1280x800) AND in reports make the same width (1280) everything shows perfectly.

If I resize Firefox window to 1024 AND set "1024" width in reports page - everything works just fine!

In any other cases: if those two value are not the same, results are not correct.
Tryed to change margin from "auto" to fixed, but no luck... IMHO the problem is with displaying results.

Also, it doesn't record clicks from Firefox 2, which are clicked on links - only on places with no links. In Explorer 7 everything is ok.

Very, VERY interresting module - great work!!!

Hoping to make this more powerful by providing mouse tracking and replay (or limit to clicks) in the uts module.

I have this exact same problem. I have tried setting the view to various screen sizes but they are all offset by what appears to be 50 px.

I noticed in your new UTS module it is more of a user opt in system (at least it sounds that way) and actually records mouse movement and activity rather then just showing a heat map.

Is there any chance of including a built in heat map module for UTS?

Also, has anyone found a patch / fix / solution for the 50 pixel problem?

Now uses minimal wrapper around ClickHeat interface, please re-open if still an issue.

Woops

Just wanted to say thanks :)

Automatically closed -- issue fixed for 2 weeks with no activity.