Allow Google Docs context menu paste
Categories
(Web Compatibility :: Site Reports, enhancement)
Tracking
(Not tracked)
People
(Reporter: 16tdmabsi, Unassigned)
Details
Attachments
(1 file)
|
30.92 KB,
image/png
|
Details |
User Agent: Mozilla/5.0 (Android 13; Mobile; rv:132.0) Gecko/132.0 Firefox/132.0
Steps to reproduce:
Open Google Docs, try to paste something using their context menu.
Actual results:
"Please, use Ctrl-C/Ctrl-V/Ctrl-X".
Expected results:
The pasted content, just that.
I think implementing this would be wonderful, it's been 17 years.
Comment 1•1 year ago
|
||
The Bugbug bot thinks this bug should belong to the 'Fenix::General' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
(In reply to BugBot [:suhaib / :marco/ :calixte] from comment #1)
The Bugbug bot thinks this bug should belong to the 'Fenix::General' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
No, it is Firefox Desktop.
Comment 3•1 year ago
|
||
When I try to use the Paste from the context mention with Chrome (technically Chromium as I'm on Linux) I get the attached image asking me to install an extension. (I haven't clicked Install so I don't know what extension it is.)
Some approaches to fix this issue:
- Convincing Google to port the extension to Firefox and use it.
- Porting the extension and convincing Google to make changes to use it.
- Porting the extension and tricking the page to use the installed extension.
- Create a webcompat trick to get Google Docs to just perform the operations.
- Something else.
Approach 2 would mean continued work in maintaining the extension. Approaches 3-4 would mean ongoing webcompat work. In either case there would be periods of problems after any Google Docs change affecting the extension.
I thing the best way to start would be to file a Chrome enhancement request to support the operations on Firefox. Has anyone checked to see if such a request already exists?
Updated•1 year ago
|
Updated•1 year ago
|
Comment 4•1 year ago
|
||
It doesn't seem to be privacy-related.
Comment 5•1 year ago
|
||
This would be a duplicate of bug1869308
Description
•