Resizing an image in a block reference also resizes the original asset block
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 resizing an image asset in a block reference, the image size in the original asset block is also changed.
However, resizing the image in the original asset block does not apply the same size to its block references.
Interestingly, this issue does not occur if the image in the original asset block is resized first.
Reproduce the Bug
- Add an image asset to a block.
- Create a block reference to that block using
[[uuid]]. - Resize the image in the block reference.
- Check the image in the original asset block.
- Resize the image in the original asset block.
- Check the image in the block reference.
Expected Behavior
Resizing an image in a block reference should not affect the image size in the original asset block.
Screenshots
No response
Files
No response
Browser, Desktop or Mobile Platform Information
windows11
Logseq 2.0.1-alpha+nightly.20260916
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
Reproduce the issue on Windows 11 using the listed steps, comparing the original asset block with its [[uuid]] block reference before and after each resize. Done means resizing the reference no longer changes the original asset image size, while resizing the original continues to behave as expected for the reference.
Written by the indexing model from the issue text.
Assessment
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100