[Bug] MFM parser issues #86
Labels
No Label
a11y
Bug
Bug fix
Critical Priority
Documentation
Feature
Feature request
Held for next release cycle
High Priority
Low Priority
Medium Priority
Minor change
Translation/Locale
WIP
No Milestone
No project
No Assignees
5 Participants
Notifications
Due Date
No due date set.
Depends on
#96 Fix code blocks not working in MFM
AkkomaGang/akkoma-fe
Reference: AkkomaGang/akkoma-fe#86
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
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?
there are currrent mfm parser issues:
example posts are: https://myfriendsare.gay/notice/AM3UOQjPrKCqF8t0L2
this post lists all common mfm things, many of which do not seem to work.
List of working mfm tags:
sparkle, bounce, jump and blur are correctly tokenized and just need to be handled by pleroma-fe (fun fact, in Misskey sparkle is entirely handled by Misskey itself and not the mfm.js library, meaning it's.. nonstandard???)
plain is deliberately unsupported in marked-mfm, in favor of standard markdown backslash escaping (not yet pushed to pleroma-fe, i'm holding that version until i fix some other stuff)
center is annoying and i'm gonna fix it hopefully
small and quote...
i don't know what the deal with those are honestly, they work in the dingusUPDATE it's probably html encoding<
>
into<
>
and not letting them parsei think inline code works, you just omitted the last ` on that line
codeblock... h, that bug looks annoying
inline code yeah you're probably right xD
center and escaped are implemented in marked-mfm 0.5.0
small is fixed in a backend branch that needs to be merged
quote is a backend thing, might wanna open an issue there
sparkle, bounce, jump and blur are frontend
i'll look into codeblock later
I'm reporting that the <> characters can erase words, sentances (with spaces), and paragraphs (with line breaks) that are not valid tags, which does not match the behavior of MFM on Misskey; the erased tag does show correctly on Misskey
(We don't run an instance so it feels kind of silly to make an account here but we were told to)
-Nim
explained more clearly on fedi but this is not an mfm thing and it's expected (though slightly weird) behaviour
@floatingghost Status with backend MFM parser?
backend parser is working, and honestly we shouldn't care that much about matching misskey behaviour 1-to-1, since it does a lot of things that make no sense
posting things between
<
and>
should indeed get stripped since you've made an HTML tagclosing since MFM is handled in the backend through
mfm-parser