mirror of
https://github.com/BoostIO/BoostNote-App.git
synced 2026-04-27 05:15:56 +03:00
[GH-ISSUE #749] Can't copy code block if no type specified #390
Labels
No labels
android 🤖
assigned to core 🦹
bug 🐛
documentation 📚
documentation 📚
duplicate 🚫
external issue 🔼
external issue 🔼
feature request 🌟
funded on issuehunt 💵
help wanted 🆘
improvement request 🔨
improvement request 🔨
ios 🍎
mobile 📱
needs investigation 🔬
needs more info ℹ️
needs specs 📐
plugin idea 🔌
plugin idea 🔌
poll 🗳️
pull-request
question ❓
rewarded on issuehunt 🎁
security issue 🔑
won’t fix ❌
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/BoostNote-App#390
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @myicq on GitHub (Dec 29, 2020).
Original GitHub issue: https://github.com/BoostIO/BoostNote-App/issues/749
Current behavior
If you do not specify a type for a code fence, the text won't get copied to clipboard, even if icon to copy is there.
Text is displayed as code block.
Expected behavior
Copy icon to work when it's there.
Steps to reproduce
Make a code block without type:
Go to preview. Copy icon is there, but no "save" icon. Copy icon does not work.
Go back to edit, and put type:
Now the copy icon and save icon are both there, and text can be copied.
Environment
Win10, 64 bit, Boostnote 0.12.3
Desktop/Web
Boost Note 0.12.3, Win10 64 bit.
@myicq commented on GitHub (Dec 29, 2020):
NOTE: found that this is a duplicate of issue #585, but confirmed for latest version and on Windows platform.
@Komediruzecki commented on GitHub (Dec 29, 2020):
Hi myicq,
I think this was forgotten so I created a bugfix, you can track it here: #750
@Komediruzecki commented on GitHub (Jan 6, 2021):
Since #750 is merged, I'll close this issue. The fix will be available in the next release.