Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

'Copy / Export as..' has broken checkboxes

Closed Beginner friendly
#1,460 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
72/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
electron
Domain
frontend

Research direction

Start by locating the “Copy / Export as..” dialog and the checkbox controls near its bottom, then trace how checkbox clicks update the preview. Reproduce by highlighting notes, opening the dialog from the context menu, and toggling a checkbox twice. Done when each checkbox can be enabled and disabled and the preview follows its state.

Written by the indexing model from the issue text.

Description

Search first
  • I searched and no similar issues were found
What Happened?

I wanted to copy a few blocks as text to send to someone, so I highlighted the blocks and clicked 'copy / export as..'. I clicked one of the checkboxes 'newline after block' to see how the preview would change, but when I tried to unselect it, it wouldn't work. I tried the other checkboxes too, but then those got stuck as well.

Reproduce the Bug
  1. Highlight notes
  2. Right-click and select 'Copy / Export as..'
  3. Click to enable any of the checkbox buttons near the bottom (like 'newline after block')
  4. Click to disable the same checkbox --> the box doesn't get unchecked
Expected Behavior

I would expect that clicking a checkbox should enable, then disable it. But it just stays enabled.

Screenshots

No response

Files

No response

Browser, Desktop or Mobile Platform Information

App Version: 2.0.2
Git Revision: 533ac43
Platform: Mozilla/5.0 (Windows NT 10.0 Win64 x64) AppleWebKit/537.36 (KHTML like Gecko) Logseq/2.0.2 Chrome/148.0.7778.180 Electron/42.3.0 Safari/537.36
Language: en-US
Plugins:

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!)
Dominant language
No language data
Stars
28
Forks
2
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from logseq/db-test

All issues in logseq/db-test

Similar issues

More Web Dev issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.