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 340583 - JavaScript Does Not Work with Right Click Features
JavaScript Does Not Work with Right Click Features
Status: RESOLVED FIXED
Product: epiphany
Classification: Core
Component: [obsolete] Backend:Mozilla
git master
Other All
: Normal enhancement
: Ephy/XR
Assigned To: Epiphany Maintainers
Epiphany Maintainers
: 482395 486020 541108 (view as bug list)
Depends on: 303287
Blocks: 603326
 
 
Reported: 2006-05-04 02:47 UTC by Bjorn Tipling
Modified: 2011-10-10 19:31 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Bjorn Tipling 2006-05-04 02:47:36 UTC
Please describe the problem:
Epiphany context menu is not accessible to JavaScript.

Steps to reproduce:
1. Go to
http://online.wsj.com/article/SB114539470915529124.html?mod=Home_US_Highlights
with Firefox. 
2. Highlight a word and righ click.
3. Observe a DOM Pop-up.,
4. Repeat steps with Epiphany
5. Oberve no such DOM pop-up.

Actual results:
Epiphany does not produce a DOM pop up like other Gecko browsers.

Expected results:
A DOM pop up that renders as it does in Firefox.

Does this happen every time?
Yes.

Other information:
This functionality has legitimate uses, as on the Wall Street Journal web page.
It's not just for advertising.
Comment 1 Reinout van Schouwen 2006-05-06 12:45:38 UTC
Thanks for your report! 

Epiphany blocks web page access to the context menu intentionally. Web pages have no business changing the context menu of the browser. While the WSJ website might not have bad intentions, the disadvantages of allowing a website to alter the browser UI would outweigh the gains by far.

Unless it's possible (I don't know) to make an extension that would allow per-site tuning of context menu access, I think this bug is a "wontfix".
Comment 2 tali 2006-12-21 07:36:34 UTC
For AJAX applications that look like a desktop application it really makes sense to define their own context menu.
If there are concerns about sites that hijack it in order to stop you from doing what you want you can define some Shift-Right-Click or something to _always_ get the default context menu. But if the user _wants_ to see the sites context menu, he should be able to do so.
Comment 3 Reinout van Schouwen 2007-03-28 23:04:56 UTC
<chpe> galeon has code for a pref about this, it's simply moving the event processing from capture to bubble phase. so it's easy to do
Comment 4 Reinout van Schouwen 2007-08-10 15:23:14 UTC
marking NEW.
Comment 5 Reinout van Schouwen 2007-10-02 07:57:42 UTC
*** Bug 482395 has been marked as a duplicate of this bug. ***
Comment 6 Reinout van Schouwen 2007-10-14 22:13:25 UTC
*** Bug 486020 has been marked as a duplicate of this bug. ***
Comment 7 Jason Clinton 2008-02-14 21:57:36 UTC
What kind of patch would you be willing to accept for this bug? IMO, JavaScript right-click needs to be allowed by default with a gconf key for admins to block capture if they so choose. But, I would be willing to write a patch that does the opposite: default is current behavior, UI option to allow sites to use right-click.

I reached the limit of my patience level on this one today: both Zimbra and Google Docs do not work with Epiphany due to this arbitrary decision. I would like to continue using Epiphany but it not working with AJAX web-sites is starting to get in the way... The web is the way it is and if we want to continue to allow Epiphany to surf the web, this feature must be allowed.
Comment 8 Reinout van Schouwen 2008-02-28 14:23:14 UTC
Jason, you may want to join this thread: http://mail.gnome.org/archives/epiphany-list/2008-February/msg00022.html

Thanks!
Comment 9 Jason Clinton 2008-02-28 21:27:44 UTC
I like the white list proposal. I'll wait for the dust to settle on xulrunner-1.9. I'll take a look at it once I have an Epiphany built against 1.9.
Comment 10 Reinout van Schouwen 2008-07-02 19:57:48 UTC
*** Bug 541108 has been marked as a duplicate of this bug. ***
Comment 11 Xan Lopez 2009-02-27 12:55:01 UTC
This works in Epiphany/WebKit now. Someone can open a bug to add a preference to undo the behavior.
Comment 12 Reinout van Schouwen 2009-03-02 13:17:00 UTC
(In reply to comment #11)
> This works in Epiphany/WebKit now. Someone can open a bug to add a preference
> to undo the behavior.

Do we need a preference for that? Can't we be a bit smarter and always offer a "way out" for sites that modify default context menu behavior?
Comment 13 Jeremy Nickurak 2009-12-25 22:36:42 UTC
Has this regressed in 2.29.x? I'm on 2.29.3, and I can't get Google Maps' context menu to work...
Comment 14 Xan Lopez 2009-12-26 11:07:37 UTC
(In reply to comment #13)
> Has this regressed in 2.29.x? I'm on 2.29.3, and I can't get Google Maps'
> context menu to work...

It's fixed in master already, it will be in the next release (in early January).