After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 603326 - Epiphany deosnt use Zimbra custom context menu
Epiphany deosnt use Zimbra custom context menu
Status: RESOLVED FIXED
Product: epiphany
Classification: Core
Component: Backend
2.28.x
Other Linux
: Normal normal
: ---
Assigned To: Xan Lopez
Epiphany Maintainers
Depends on: 340583
Blocks:
 
 
Reported: 2009-11-29 19:22 UTC by Mathieu Bridon
Modified: 2009-12-14 11:27 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Mathieu Bridon 2009-11-29 19:22:05 UTC 
Zimbra uses right click for some operations (like emptying the trash).

But Epiphany opens its « regular » context menu when right-clicking on some element in Zimbra, instead of the custom context menu that Zimbra defines with JS.

This makes the « advanced » interface of Zimbra totally unusable in Epiphany as lots of actions are only accessible with this custom right click menu.
Comment 1 Reinout van Schouwen 2009-11-30 12:27:35 UTC 
This should work (see bug 340583) but apparently it doesn't.
Could you post a testcase please?
Comment 2 Mathieu Bridon 2009-11-30 19:42:02 UTC 
(In reply to comment #1)
> This should work (see bug 340583) but apparently it doesn't.
> Could you post a testcase please?

What kind of test case would you like?

Way to reproduce it is :
1. open Zimbra in Epiphany (you'll need an access to a Zimbra account for that :-/)
2. right-click on the trash
Comment 3 Jason Clinton 2009-12-08 02:20:40 UTC 
Any Google Docs document editor is a test case.
Comment 4 Gustavo Noronha (kov) 2009-12-14 11:27:57 UTC 
I pushed a31c25320318115914e009048a4081b2a1b58f50 fixing this problem for pages I have access to, at least. You need WebKit from trunk to have some web pages work fully, though. There might be bugs still, for some more exotic pages. If you find those, please file bugs in WebKit, under the WebKitGtk component!