Editor improvements #486
No reviewers
Labels
No labels
A: API
A: Backend
A: Federation
A: Front-End
A: I18N
A: Meta
A: Security
Build
C: Bug
C: Discussion
C: Enhancement
C: Feature
Compatibility
Dependency
Design
Documentation
Good first issue
Help welcome
Mobile
Rendering
S: Blocked
S: Duplicate
S: Incomplete
S: Instance specific
S: Invalid
S: Needs Voting/Discussion
S: Ready for review
Suggestion
S: Voted on Loomio
S: Wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Plume/Plume#486
Loading…
Add table
Reference in a new issue
No description provided.
Delete branch "editor-improvements"
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?
TODO:
If I may add to the todo list: https://github.com/Plume-org/Plume/pull/458#issuecomment-473323102
Codecov Report
@fdb-hiroshima Yes, the first one is already fixed, I'll see for the other. :)
I think basic-editor should be permanent, and there would then be a button to re-enable the "advanced" editor
I don't really know how to name it…
rich text editor?
It's a bit sad markdown does not work with the rich editor (cmark see some div so it assumes it's only html and does not attempt to parse markdown)
@fdb-hiroshima This should definitely be fixed before merging this branch I think. I will see what I can do.
The only fix I see is, given the following :
Where we are given a single
Html("<div>some text</div><div></div>")
, we could cut it out as["some text", ""]
, call cmark on each of these, and put back thediv
sI was more thinking of pre-processing the HTML with the DOM APIs in WASM, because your solution may break footnotes, or links that use this syntax:
please remove the callgrind output files from the PR