[Bug] MFM parser issues #86

Closed
opened 2022-07-31 16:21:40 +00:00 by Beefox · 8 comments
Contributor

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:

  • Plain
  • Bold
  • Italics
  • Small
  • Quote
  • Center
  • Inline code
  • Code block
  • Flip
  • Font
  • x2
  • x3
  • x4
  • Blur
  • Jelly
  • Tada
  • Jump
  • Bounce
  • Spin
  • Shake
  • Twitch
  • Rainbow
  • Sparkle
  • Rotate
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: - [ ] Plain - [x] Bold - [x] Italics - [ ] Small - [ ] Quote - [ ] Center - [ ] Inline code - [ ] Code block - [x] Flip - [x] Font - [x] x2 - [x] x3 - [x] x4 - [ ] Blur - [x] Jelly - [x] Tada - [ ] Jump - [ ] Bounce - [x] Spin - [x] Shake - [x] Twitch - [x] Rainbow - [ ] Sparkle - [x] Rotate
Contributor
  • 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 dingus UPDATE it's probably html encoding < > into &lt; &gt; and not letting them parse

  • i think inline code works, you just omitted the last ` on that line

  • codeblock... h, that bug looks annoying

- 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 dingus~~ UPDATE it's probably html encoding `<` `>` into `&lt;` `&gt;` and not letting them parse - i think inline code works, you just omitted the last ` on that line - codeblock... h, that bug looks annoying
Author
Contributor

inline code yeah you're probably right xD

inline code yeah you're probably right xD
Contributor

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

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
nbsp added a new dependency 2022-08-01 14:54:25 +00:00
eris added the
Bug
label 2022-08-01 18:04:37 +00:00

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

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
Contributor

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

> 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
Member

@floatingghost Status with backend MFM parser?

@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 tag

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 tag
Contributor

closing since MFM is handled in the backend through mfm-parser

closing since MFM is handled in the backend through `mfm-parser`
nbsp closed this issue 2022-12-13 15:36:21 +00:00
Sign in to join this conversation.
No Milestone
No project
No Assignees
5 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Depends on
Reference: AkkomaGang/akkoma-fe#86
No description provided.