Selection in Grid is not picking up location of mouse properly

If it helps, this is an integration with Angular (1.x), so I am creating the  Flexmonster component with the “fm-pivot” directive. 
 
My DIV containing the directive looks like this
 
 
    <div fm-pivot
         fm-width="100%"
         fm-height="100%"
         fm-toolbar="true"
         fm-license-key="{{flexmonsterLicenseKey}}"
         fm-ready="onAlertFlexmonsterReady(pivot)"
         fm-before-toolbar-created="customizeToolbar(toolbar)"
         id="alertPivotContainer">
      </div>
 
I’ll see what I can do about make a sample, but my time is limited.
 
I did add an event handler for “fm-cell-click” and it is reporting the correct row and column selection.  It is only the grid itself that that is showing the wrong selection

Tanya,
Just ran it in JSFiddle and it works as expected IF you start with a defined report.  If you REMOVE the "fm-report=report" from the directive, and re-run it you will see strange behavior.  Not having a selected report is the state of our Flexmonster component, when the component is initially displayed. Any way. I am not seeing the exact same strange behavior that I see in my application, but similar.  Here is what I see (again, with no report defined)
 

• Click over r1,c1 and r2,c1 is selected (if you select at the very top of a cell, then the cell is selected)
• Click in header of column 3 (or any column) and instead of the entire column being selected, only the first cell on row 1 is selected
• Click in the column header close to the right side (but before the cursor changes to the "move" column cursor) and the column to the right is selected, not the one the mouse id over.
• When I attempt to resize a row and 'grab' the row divider to resize it, as I move it down just a bit, the row divider jumps down one full row height.  Resizing a column also has a similar jump, but not as pronounced.

 
Lastly, in addition to using Angular, we are also using the component library jQWidgets.  jQWidgets has Splitter component.  In our application, the Flexmonster component is displayed int the right panel of the 'splitter'.  I don't know if this affects anything, but it is an addition difference in our environment from a pure Angular only environment.  BTW, jQWidgets fully supports the Angular framework and this is the same environment & layout we are currently using with FLexmonster 2.3 which does not demonstrate these problems

As the name implies, jQWidgets, requires the use of jQuery.  Since you guys have removed that dependency, perhaps there is now some compatibility issues