-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Logseq whiteboard bug #9439
Comments
@JinQisMe Hello! Thanks for the report. I cannot reproduce the issue. Does this happen on the latest version of Logseq? Is the width of the blocks reverted, whenever you resize them and reload the Whiteboard? Could you please also provide step by step instructions or maybe a video recording? |
Hi, This bug is happening every time!Please see the attached video recording. I am using the latest version of Logseq. Uploading Logseq Bug20230524_104354.mp4… |
attached video recording
|
@JinQisMe Thanks for the screen recording. A fix will be released soon. |
Please do let me know when it‘ve been fixed. It is important for me.
…------------------ 原始邮件 ------------------
发件人: "logseq/logseq" ***@***.***>;
发送时间: 2023年5月24日(星期三) 下午4:50
***@***.***>;
***@***.******@***.***>;
主题: Re: [logseq/logseq] Logseq whiteboard bug (Issue #9439)
@JinQisMe Thanks for the screen recording. A fix will be released soon.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Search first
What Happened?
The floating text boxes added to Logseq's whiteboard always automatically shift to the right leaving a large blank space when close and opened the whiteboard next time. And the alignment of the arrows also becomes messy.
Reproduce the Bug
close and opened the whiteboard next time
Expected Behavior
All elements stay right how I design the whiteboard for all the time.
Screenshots
Desktop or Mobile Platform Information
Win 11 desktop
Additional Context
No response
Are you willing to submit a PR? If you know how to fix the bug.
The text was updated successfully, but these errors were encountered: