This is a frustrating bug, and it reveals something deeper about how fragile our productivity tools really are. When a Firefox user cannot paste values into Google Sheets using Ctrl+Shift+V, the entire rhythm of work breaks. The user who posted this knew exactly what they needed: paste values only, no formatting. They checked the browser config, found the relevant setting already enabled, and still hit a wall. That is not a user error. That is a tool failure.
What makes this story notable is how specific and practical the workaround is. Double-click the cell, then paste. It works sometimes. That is not a fix, it is a concession. The user is adapting to the software, not the other way around. And that is the wrong direction. Spreadsheets should empower users to move data freely, not force them to hunt for hidden settings or memorize awkward keyboard sequences. The fact that Ctrl+C and Ctrl+V work but strip away the user's control over formatting means the browser is interfering with a deliberate workflow choice. The tool is deciding what the user needs, and getting it wrong.
This is where the conversation should turn. The user's issue is not unique to Firefox, nor is it exclusive to Google Sheets. It is a symptom of a larger pattern: legacy tools and platforms that treat data movement as an afterthought. Copying and pasting should be seamless, whether you are working in a spreadsheet, a web app, or a plain text editor. When it breaks, productivity stalls. And the fix should not require a Reddit thread, a browser config toggle, or a double-click dance. It should be as simple as selecting "Paste values only" and watching it work.
Our take is straightforward: this bug is a warning sign. If a core function like paste-values-only fails on a major browser with a dominant spreadsheet tool, the system is not as robust as users deserve. The solution is not to wait for a patch from Mozilla or Google. It is to explore tools that treat data integrity as a priority, tools that let you move information without fighting the interface. For now, the user's workaround is the best they have. But it should not be the final answer.