Bug: Paste fails on Firefox due to asynchronous clipboard read (NotAllowedError)
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 28
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
Search first
- I searched and no similar issues were found
What Happened?
When attempting to paste text or content into the Logseq web app on Firefox, the paste operation fails, and the following error is thrown in the developer console:
DOMException NotAllowedError: Clipboard read operation is not allowed.
This issue occurs because Logseq attempts to read the clipboard asynchronously (e.g., using navigator.clipboard.read or readText) after the initial paste event. Firefox has a strict security policy that blocks any asynchronous clipboard read operations unless a specific development flag (dom.events.testing.asyncClipboard) is enabled in about:config, which is insecure for daily use.
Unlike Logseq, most other web apps (like Notion, GitHub, etc.) handle pasting successfully on Firefox because they extract the clipboard data synchronously within the native paste event handler.
Reproduce the Bug
- Open Logseq Web app (e.g., https://test.logseq.com/ or a self-hosted instance) using Firefox.
- Copy any text from an external source.
- Click on a block in Logseq and press
Ctrl + V(orCmd + Von macOS) to paste. - Notice that nothing is pasted into the block.
- Open the browser's Developer Tools (F12) -> Console, and you will see the
NotAllowedError: Clipboard read operation is not allowed.error.
Expected Behavior
Pasting should work seamlessly on Firefox without requiring users to change risky about:config settings.
To resolve this fundamentally, Logseq should be updated to extract clipboard data synchronously within the paste event handler using e.clipboardData.getData('text/plain') (and 'text/html'), rather than requesting it asynchronously later via the Clipboard API.
Screenshots
No response
Files
No response
Browser, Desktop or Mobile Platform Information
Firefox 150.0.1
https://test.logseq.com/ (2026-06-05)
Additional Context
No response
Are you willing to submit a PR? If you know how to fix the bug.
- I'm willing to submit a PR (Thank you!)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file or test is identified. Start by locating Logseq's paste event handler and any asynchronous navigator.clipboard.read or readText calls, then reproduce the issue in Firefox. Done means text and HTML paste successfully in Firefox without changing about:config settings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend, web-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100