19

The new stacks editor destroys content in the most drastic way possible. It seems that if HTML tags are used the whole content is discarded.

It happens when stacks editor is enabled and you have selected the non-markdown view. When you press "edit" (both inline and in new page) the contents disappear. When you have the markdown view selected, switch it off to see everything gone. It also happens when creating a new post, but you have to switch to markdown view and back. Sandbox

Tested in Chrome 101 on Windows 10.

A sample input that causes the issue:

Any text here, doesn't matter what.

<sub>
Any text is fine here, but note the inline html tags on their own lines
</sub>
2
  • 6
    Semi-related: Toggling between Markdown and rich text to preview the result without editing anything should not be a destructive action...but even if that were fixed, this would still be extremely broken.
    – Ryan M
    Commented May 26, 2022 at 15:18
  • 8
    Yep, these sorts of complete loss of content have been reported for going on 2 years now, since the new "Stacks" editor was first previewed in Teams and SE asked for testing/feedback. It's ridiculous that they moved something into production with such glaring, known, obvious, critical issues. It's even worse that they've kept using it and both forced their paying Teams customers to use it, and forced new users on SO to use it (during one of the weeks long trials of revamping the question asking pages).
    – Makyen
    Commented May 26, 2022 at 15:54

3 Answers 3

11

Stacks editor is broken. This is the proof. Try to edit this answer if you can. If the content is shown to you in the editor, try switching "markdown" back and forth.

It will be accepted to reproduce and demonstrate the bug.
10
  • No repro, but that's because I can't switch between editors on your post. I'm assuming you've already disabled all adblockers and userscripts when testing this?
    – Mast
    Commented May 26, 2022 at 15:18
  • @Mast Why can you not switch between editors? What do you see when you open the editor in a new tab? meta.stackexchange.com/posts/379038/edit
    – Dharman
    Commented May 26, 2022 at 15:19
  • 1
    Repro'd, and if I hit "Cancel" and reopen the >2k editor, it doesn't regain its content.
    – Spevacus
    Commented May 26, 2022 at 15:19
  • 9
    @DavisBroda You need to enable the New Stacks Editor in your preferences.
    – Spevacus
    Commented May 26, 2022 at 15:20
  • Enabled the new editor in preferences, and the issue now reproduces for me. Content is completely gone upon hitting the edit button Commented May 26, 2022 at 15:21
  • If that switch is what's required, considering that feature is in Alpha, I wouldn't expect it to work 100% of the time.
    – Mast
    Commented May 26, 2022 at 15:22
  • 11
    @Mast That would maybe be fine if it weren't also the only available editor in Teams. Also, it's still a bug worth reporting, since they eventually want this for the rest of the network.
    – Ryan M
    Commented May 26, 2022 at 15:23
  • 2
    @Mast Yeah, it's ok here on Meta where you can switch it off and ignore it, but many people don't have that choice, especially on paid Teams.
    – Dharman
    Commented May 26, 2022 at 15:23
  • Looks like it breaks when the HTML tags cover multiple lines. If I edited it to inline <sub>It will...</sub>, it doesn't. Commented May 26, 2022 at 15:47
  • 3
    @Mast While the editor may be pre-alpha quality, it's been in production on Teams for well over a year. It was first pre-alpha'd about 2 years ago, which was when bugs like this one, where the entire contents of the post are lost, were first reported.
    – Makyen
    Commented May 26, 2022 at 15:57
10

Thank you for the report. I've filed this issue in the Stacks-Editor GitHub repo so we can triage and keep better track of it. I was able to reproduce this issue and I have a pretty good idea of where to start looking, so I marked this post as .

Short version - HTML in CommonMark is a beast to get right and only assumes one way translation (CommonMark → HTML). In our best effort attempts to make HTML content editable in rich text mode, the tokenized output is getting mangled a little bit and is failing to import into the rich text editor's node schema.

1
  • 1
    Yeah, there's some oddity when you try to wrap a markdown list with <sup>. it's not the only thing here, but it does seem to play into this issue
    – Machavity
    Commented May 26, 2022 at 18:23
7

This is fixed. It was included in the beta 1 release.

HTML tags
on same lines or different ones
discard text no more

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .