Live data from Hacker News

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

bugzilla.mozilla.org

51–60 of 99 posts

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

#51

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…

I can reproduce. Firefox 127.0 under wayland, arch linux

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

#52
Oh my God! I thought it was just me and some silly "we only enable copy for sites without iframes (or something security related) feature". I was quietly hoping someone here had the secret "type 'unprotected pasted' in the devtools console" solution

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

#54
This happens often enough to notice (I have seen it a few times) but not really often enough to seriously frustrate me. At least on Wayland it's enough to unfocus and focus the Firefox window for me, then Copy is not greyed out anymore.

I know the kneejerk reaction is "how could something so basic be broken in any way???" but realistically I think it's just a testament to how complex the entire codepath of something as simple as a "copy" menu item has gotten. I mean reading the bug report, it looks like it weaves in and out a surprising number of different components in complex ways involving IPC. It makes sense but at the very least I still never think of a simple UI element like a copy button having this much going on.

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

#55
post #38

I switched to Edge because of this bug.

"I got annoyed with the occasional inability to use the 'Copy' menu item and couldn't fathom training my muscle memory to instead use ctrl+c, so I switched to a browser that spies on me and actively ignores my consent." I really don't get how people work, sometimes. Stuff like this tells me the privacy fight is just completely unwinnable. It's not even that people don't care; people actively make choices that make th…

I mean, yeah I don't care if Microsoft realizes I'm a parent and want to buy diapers. I've been using Firefox since it was version 0.1 and was called Phoenix, and I used it because it was better than Internet Explorer 6 and had themes and add-ons and tabbed browsing.

Current Firefox hasn't introduced anything unique to the browser and that's why their share is continuing to dwindle. Edge supports vertical tabs natively without any weird hacks to userchrome.css. Arc has an easy way to hide all browser chrome as well as "mini Arc" for different pages. Vivaldi has mouse gestures, etc.

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

#56
post #17

They're also deleting downloaded .pdf whilst in private mode. Yes even when I click save as. It gets downloaded to my downloads folder and then sometimes it's deleted when I close the browser. Sometimes.

It's not a bug, it was designed this way: https://bugzilla.mozilla.org/show_bug.cgi?id=1790641#c11 That being said, I hate it, it's awful UX. If something is in the "Downloads" folder, it should never be automatically removed, it's not "Temp". Not to mention that there's absolutely no indication in the UI that your downloads will be deleted. Also, there's no obvious way to make the downloaded file permanent, other th…

Comment on the bug. Private mode should save to a Downloads/temp folder, and the Download/Save UI should offer an "export/keep" function.

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

#57

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…

https://streamable.com/adh0t3

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

#58
post #48

Not sure why this is big news, big enough to be in the #1 spot right now. From reading the comments on the bug, it seems to be an issue that's hard to reliably reproduce, and -- despite how simple it sounds from the editorialized HN title -- it involves interactions between different parts of the browser, and it's hard to track down and fix. Nonetheless, there are some proposed fixes, and I expect a near-future relea…

i thought i was crazy but had enough times where copying didn't work and i thought it was my computer but seems i wasn't crazy

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

#59

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…

I can reproduce. Firefox 127.0 under wayland, arch linux

Which compositor? I'm trying on 127.0.2 and can't seem to do it, and I'm on kwin_wayland.

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

#60

Overall, Firefox is wonderfully fantastic these days. I can see how this is frustrating to some, but sometimes that's how the priority nets out. It looks like the bug was triaged, investigated, took its time finding its way to the right developers, and now a fix will land soon. This is mostly just the process working. I for one, am grateful for these folks' good work.

Yet this is a single example that actually was resolved, while far from the only inconsistencies and bugs.

While from an engine side, the situation with bugs lingering for years, and web features that still can't be used way, way after even Safari managed to implement them is not insignificant.

It's not broken or actually bad software, but it's struggling to keep up with the Browsers it's meant to be an independent alternative for.

This makes UX and feature parity a HUGE concern!

Loosing market share through inconveniencing users in turns means web devs will have increasingly less incentive to. work around it's quirks and issues, which even further shifts the Browser market towards a handful of huge, profit oriented companies - which is without exaggeration a threat to maintaining an open web.

Post reply on HN