Live data from Hacker News

Copy and Paste context menu entries sometimes disabled when they should not be

bugzilla.mozilla.org

1–10 of 99 posts

Re: Copy and Paste context menu entries sometimes disabled when they should not be

#2
Specifically the right-click menu option, which is often greyed out for no apparent reason. This happens on both Windows and Linux. Ctrl+C still works, but how does Firefox break something as basic as the right-click menu and copy in 2024?

Re: Copy and Paste context menu entries sometimes disabled when they should not be

#3

Specifically the right-click menu option, which is often greyed out for no apparent reason. This happens on both Windows and Linux. Ctrl+C still works, but how does Firefox break something as basic as the right-click menu and copy in 2024?

[flagged]

Re: Copy and Paste context menu entries sometimes disabled when they should not be

#4

Specifically the right-click menu option, which is often greyed out for no apparent reason. This happens on both Windows and Linux. Ctrl+C still works, but how does Firefox break something as basic as the right-click menu and copy in 2024?

The website you are visiting might be breaking it. There are many sites which will force that option to grey out upon right-click.

This is by design.

Re: Copy and Paste context menu entries sometimes disabled when they should not be

#5

Specifically the right-click menu option, which is often greyed out for no apparent reason. This happens on both Windows and Linux. Ctrl+C still works, but how does Firefox break something as basic as the right-click menu and copy in 2024?

The website you are visiting might be breaking it. There are many sites which will force that option to grey out upon right-click. This is by design.

Many websites will also prevent highlighting text as well. Reader mode is helpful for that.

Re: Copy and Paste context menu entries sometimes disabled when they should not be

#6
From the bug report:

    1. Open https://www.google.com/ in a tab

    2. Open https://ftp.mozilla.org/pub/firefox/nightly/ in the same tab

    3. Click on Go back button (or Alt+Left Arrow)

    4. Click on Go forward button (Alt+Right Arrow)

    5. Select some text

    6. Right click
It doesn't seem like it's a website doing something it shouldn't be and breaking RFC. It's really a bug in firefox.

Also, the scope is very specific and kinda justifies it being low priority. Maybe.

Note that there is another reproduction step sequence that I chose not to put in this comment for the sake of simplicity.

Re: Copy and Paste context menu entries sometimes disabled when they should not be

#7

Specifically the right-click menu option, which is often greyed out for no apparent reason. This happens on both Windows and Linux. Ctrl+C still works, but how does Firefox break something as basic as the right-click menu and copy in 2024?

Because the bug involves sending and receiving messages to multiple other processes. Each webpage you visit is potentially in a different process, and each of those processes maintains its own selection state (that state is visible to javascript running in the page, and you don't want to leak what you copy on this page to any other, so it would be hard to put it anywhere else). There is only one context menu though (in the main process), so it has to send a message to the content process to find out if anything is selected or not. It seems that somehow the message is going to the wrong content process, to a page where nothing is selected. The context menu itself then displays exactly the right thing, based on the data it got back.

Re: Copy and Paste context menu entries sometimes disabled when they should not be

#8

Specifically the right-click menu option, which is often greyed out for no apparent reason. This happens on both Windows and Linux. Ctrl+C still works, but how does Firefox break something as basic as the right-click menu and copy in 2024?

The website you are visiting might be breaking it. There are many sites which will force that option to grey out upon right-click. This is by design.

It's the duty and responsibility of a properly implemented browser to not allow a "website" to break basic UI functionality because it pushes some javascript. I don't care about how Safari and chrome and edge do it. Firefox should not follow their lead.

This is a fine example of why people install plugins like ublock origin and similar.

Post reply on HN