Spoiler tags can blow up post content or something in the text editor #6

Closed
opened 2022-11-23 22:28:23 +00:00 by Snakes · 6 comments
https://rdrama.net/h/schizocel/post/115043/justcool393-appreciation-post-marstolfo/2930456?context=8#context ![](https://rdrama.net/images/1666351662767847.webp)
Snakes added the
bug
label 2022-11-23 22:35:30 +00:00

first! xD xD

first! xD xD

first! xD xD

Second!

> first! xD xD Second!

So we have his device which is a chromebook and the browser he is running on it

Mozilla/5.0 (X11; CrOS x86_64 15117.112.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/107.0.0.0 Safari/537.36

@Snakes are we supporting non standard browsers?

So we have his device which is a chromebook and the browser he is running on it Mozilla/5.0 (X11; CrOS x86_64 15117.112.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/107.0.0.0 Safari/537.36 @Snakes are we supporting non standard browsers?

@Snakes are we supporting non standard browsers?

General rule of thumb is that if it supports animated WebP, we're willing to at least try to support it. Chrome 107, even on an odd platform, ought to qualify.

Main guess here is some sort of interaction between the inline emoji picker and the clientside Markdown engine, though unclear how exactly. Probably primarily the fault of the emoji picker, if blame's to be laid: looks like it generates an input event, then Markdown updates, which then pushes it forward one character, at which point picker thinks it hasn't inserted yet and re-inserts.

> @Snakes are we supporting non standard browsers? General rule of thumb is that if it supports animated WebP, we're willing to at least try to support it. Chrome 107, even on an odd platform, ought to qualify. Main guess here is some sort of interaction between the inline emoji picker and the clientside Markdown engine, though unclear how exactly. Probably primarily the fault of the emoji picker, if blame's to be laid: looks like it generates an input event, then Markdown updates, which then pushes it forward one character, at which point picker thinks it hasn't inserted yet and re-inserts.

@Snakes are we supporting non standard browsers?

General rule of thumb is that if it supports animated WebP, we're willing to at least try to support it. Chrome 107, even on an odd platform, ought to qualify.

Main guess here is some sort of interaction between the inline emoji picker and the clientside Markdown engine, though unclear how exactly. Probably primarily the fault of the emoji picker, if blame's to be laid: looks like it generates an input event, then Markdown updates, which then pushes it forward one character, at which point picker thinks it hasn't inserted yet and re-inserts.

https://www.groovypost.com/howto/chrome-os-android-studio/

Im going to try this out I just want to see the browser event, commenting so theres history

Itll also let me know when its fixed I guess

> > @Snakes are we supporting non standard browsers? > > General rule of thumb is that if it supports animated WebP, we're willing to at least try to support it. Chrome 107, even on an odd platform, ought to qualify. > > Main guess here is some sort of interaction between the inline emoji picker and the clientside Markdown engine, though unclear how exactly. Probably primarily the fault of the emoji picker, if blame's to be laid: looks like it generates an input event, then Markdown updates, which then pushes it forward one character, at which point picker thinks it hasn't inserted yet and re-inserts. https://www.groovypost.com/howto/chrome-os-android-studio/ Im going to try this out I just want to see the browser event, commenting so theres history Itll also let me know when its fixed I guess

Well that didnt work. @TrappyIsBae you said you are a codecel too, you see what snakes wrote, do you want to try this with me?

Well that didnt work. @TrappyIsBae you said you are a codecel too, you see what snakes wrote, do you want to try this with me?
Sign in to join this conversation.
There is no content yet.