Context menu does not work in Chrome (Safari?) for Webfm attachments

I verified this with the last Chrome 2, and the same problem exists in Safari 3. It actually works, but the content menu pops up in the body above where the WebFM section of the form is. Almost like it's y property is being set relative to that object rather than the file browsing window?

Experiencing the same problem as of 6.x-2.10-rc5.

Thanks to notabene for pointing out the popup was misplaced rather than absent! Through the miracle of the mousewheel I was able to scroll to the top of my node creation form without clicking, and lo and behold there was the context menu. Well out of context, but still usable :D

As I've stated before, I do not have access to Safari so am unable to fix. Patches from the community are always welcome.

The issue seems to be related to how WebFM interacts with Chrome in terms of mouse position. Using Chrome, if I click and hold a folder to move it, the red icon that indicates where the folder will land is far above the actual mouse position. It seems to me that an easy fix would be a Y-axis adjustment similar to the X-axis adjustment implemented for IE.

Following.

Also, sometimes the context menu appears in the part of the frame above the portion that’s visible on the screen, so sometimes it seems it’s not working at all (scrolling up reveals it). And sometimes when I click the close/X box, the window just jumps away a few pixels, without closing. Most annoying.

This feature is virtually unusable with Chrome.

Same issue with Chromium. Right click context menu still placed approximately 20% from page top to bottom no matter where the line for that file browser is.

Problem was with Drupal.mouseposition function from webfm.js
I attached a patch using some code from jquery.
Tested under chrome, firefox, and ie7/8

karolrybak,

thank you for providing this patch and helping to make webfm better. But actually I believe we have fixed this in the current beta and dev release. (Was #473918: directory automatically moved to inside another directory) Also I cannot reproduce the reported issue this with SWares Iron which essentially is Chromium.

Are you sure this is still an issue? If so I think your patch needs a little bit more explanation - the calculation just seems very confusing

Thank you.

Well it does works fine with dev release. So i guess my patch is irrelevant.

About the code: I simply took it from relevant part of jquery framework:
https://github.com/jquery/jquery/blob/master/src/event.js#L509

Guess webfm could use jquery - it makes cross browser compatibility almost non-issue.

Thanks for your response