Composer placeholder does not update when it should

AI-generated summary

Users are discussing an issue with the composer placeholder not updating correctly when switching between rich text and markdown modes. RGJ initially noticed that the placeholder text doesn’t change as expected, even though different placeholders exist for each mode. Moin confirmed seeing different placeholders, but RGJ found the update behavior inconsistent. awesomerobot identified that the placeholder only updates on page refresh and not when toggling modes. RGJ further detailed the issue, noting that after refreshing, the placeholder updates but the composer reverts to rich text. A fix was mentioned by awesomerobot and later confirmed to be merged by renato, resolving the issue.

When you open the composer, it says “Type here. Use markdown, BBCode or HTML to format” as the placeholder. However, it also says that when you’re in rich text mode. And you can’t use BBcode there, and you can’t use HTML very well. So maybe the placeholder should be different for rich text mode?

EDIT it is, it just doesn’t update when you expect it to (and it does update when you don’t expect it :wink: )

2 Likes

I see a different placeholder in rich text mode

2 Likes

Yes, I see it now, I am totally confused

Change was on July 13 UX: Update composer placeholder for RTE by martin-brennan · Pull Request #33594 · discourse/discourse · GitHub

but my 3.6.0 beta1 forum does not have it.

EDIT I get it, updating the OP

2 Likes

It seems to only work on refresh, we’ll have to see if we can make it update on toggle

2 Likes

It’s worse even,

  • I have rich text as default
  • I switch to markdown
  • Placeholder stays the same
  • I press F5
  • Placeholder becomes the markdown+bbcode placeholder but composer switches back to rich text
1 Like

We have a fix in the works here

https://github.com/discourse/discourse/pull/35382

2 Likes

This has been merged, closing…

2 Likes