joel

I ended up forking and updating the dependencies for my own reference. You could reference my fork as a starting point if it helps. Bear in mind that I usually...

@stevenbenner The positioning has been updated to use bottom for north placements. The branch has also been rebased to current tip of master.

As an aside, perhaps higher risk commits fit better in a major revision release rather than a minor one? In any event, it turns out that some webpages position the...

The technique is the same but the compensation calculation code was significantly restructured. In order to check body and html tags in turn the CSS position check and offset calculation...

Good catch, thank you. Not sure why I did not notice the offset. It seems that when calculated as I intended that the el*WithMargin and the elPositionPx terms all cancel...

I added the position settings to edge-cases. It works fine for body but not for the html tag. The jquery offset returns left: 0, top: 0 even when the html...

(Rebased to current master. It appeared there was no conflict between this patch and the diff to master.) Thanks for your review and feedback on this issue. I be out...

The compensation calculations and collision detection have been completely revamped. I also took your suggestion to move the compensation computation into CSSCoordinates. The collision detection has been revised to use...

I understand your concern. To avoid inadvertently breaking code, perhaps we can make it an optional feature that could be enabled for those who encounter the problem and need a...

I am looking forward to this feature. I am a little concerned about distinguishing between network error + data and a terminating network error. I typically need to take alternative...