Why does fast edit often open the composer instead?

Product Support

AI-generated summary

In a support discussion titled “Why does fast edit often open the composer instead?”, Aizada_M reports that selecting text for fast edit consistently opens the full composer, questioning whether the feature only works on recent posts. Canapin explains that fast edit fails and falls back to the composer when the selected text contains elements that make precise editing ambiguous — such as special characters (e.g., fancy quotes), markdown formatting, pipes (|), line breaks, non-ASCII characters, or text that appears more than once in the post. A screen recording is shared to illustrate the issue with quote characters. The behavior, while sometimes obscure, is by design to avoid unintended edits when context is unclear.

1

Hi!
Great feature :clap:, but for some reason, when I select a piece of text for editing on my site, the composer window always opens. Or does it only apply to recently created messages?

2

It happens when there is content in the sentence that prevents fast edit from knowing exactly the area you’re trying to edit. I admit it is sometimes a bit obscure. It can be because there’s a special character in the sentence or stuff like this.

For example, trying to fast edit “this special” sentence when the content is fairly close to the quotes, I don’t know the details) will fail because of the fancy quotes.

It can also happens if there’s markdown formatting in the sentence.

edit:

Other conditions for fast edits to work are when the selection doesn’t:

  • contains | (table)
  • contains line breaks
  • contains non-ascii chars
  • appears more than once in the post