You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ngContextMenu calculates coordinates wrongly when is placed inside of row template in UIGrid even with position:absolute. I think it takes grid's coordinates instead screen's.
The text was updated successfully, but these errors were encountered:
Yep – absolute is a whole different scenario, as it's relative to the UIGrid, so although it gets the correct coodinates, the values aren't relative to its container.
I'll have to think about that, as ngContextMenu is designed to work with position: fixed which doesn't suffer from the same complexities as absolute.
I just made a workaround to fix the Position of the ContextMenu by subtracting pixel scroll distance "$(window).scrollTop()" from the y Pos (in Line 137, uncompressed file).
ngContextMenu calculates coordinates wrongly when is placed inside of row template in UIGrid even with position:absolute. I think it takes grid's coordinates instead screen's.
The text was updated successfully, but these errors were encountered: