mirror of
https://github.com/BoostIO/BoostNote-App.git
synced 2026-04-27 05:15:56 +03:00
[GH-ISSUE #389] Option to allow HTML tag rendering #172
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#172
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 @Rokt33r on GitHub (Mar 27, 2020).
Original GitHub issue: https://github.com/BoostIO/BoostNote-App/issues/389
Currently we're sanitizing every html contents by default. But using some html tags, like
<img>, are quite common. So we can provide three option like the old app.If you really want this, please click 👍 then we prioritize this issue.
@derekantrican commented on GitHub (Mar 27, 2020):
I'd vote for something like "sanitize only dangerous". I think, at a minimum, the basics should be allowed: headings, link, image, bold, italic, underline, etc. They should also be allowed inline (for instance:
here is text that is <u>under</u>lined)@Rokt33r commented on GitHub (Mar 27, 2020):
I agree with you. The second option should be default. I'll update the body.
@frenchiveruti commented on GitHub (May 3, 2020):
Sanitize only dangerous contents(XSS) (default)
I agree.
@arcturus140 commented on GitHub (May 3, 2020):
to me it is mostly important to have my existing notes from the old app being correctly represented.
it's not something I essentially need otherwise. I don't understand why there are 3 options presented to the user. Is there really the need for the user to have control over this?
@Rokt33r commented on GitHub (May 4, 2020):
Good point. Now I'm thinking to provide the 2nd option only. Then I guess we could know the demands for the last options.
@Cryo99 commented on GitHub (Jun 2, 2020):
I agree that we definitely need to be able to enter HTML tags into the Markdown and have them rendered correctly. Indeed, Markdown is predicated on this. Not being able to use tags in the Markdown to manage behaviour that isn't covered by it, such as font colouring, strikeththrough, etc., would be a major limitation.
@techbecca commented on GitHub (Jun 28, 2020):
I found this issue by searching for why the folding block syntax isn't working properly. Will this issue solve that?
@Flexo013 commented on GitHub (Jul 11, 2020):
@techbecca I imagine it will.
@merovingienne commented on GitHub (Sep 28, 2020):
@Rokt33r As per this comment on PR 561, does Boost Note support HTML tables in notes?
I haven't been able to get it to work properly. The editor correctly identifies the syntax and highlights it, but the live preview does not render it. HTML exports also have the same issue.
Platform: macOS 10.15.6 (19G2021)
Boost Note version: 0.9.0
@Flexo013 commented on GitHub (Sep 28, 2020):
@merovingienne HTML tables are not supported as they can be fully created using the markdown format. If there is a large demand for the feature then it's something we will consider.
(Also feel free to create a new issue with the feature request for HTML table tag support.)
@merovingienne commented on GitHub (Oct 8, 2020):
@Flexo013 thank you for the response!
My use case is to have a list of items within a table cell. This can be easily achieved with HTML tags in old Boostnote, and I was confused by the comment that all HTML tags allowed on GitHub are supported.
Cool, I'll create a new issue :)