{"version":"2.1.223","anchor":"feedback-form-gets-a-real-multi-line-details-editor-and-a-si","canonical_anchor":"feedback-form-gets-a-real-multi-line-details-editor-and-a-si","heading":"Feedback form gets a real multi-line details editor and a size limit message","tier":"notice","area":"Feedback Form","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223\/e\/feedback-form-gets-a-real-multi-line-details-editor-and-a-si","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223","markdown":"### Feedback form gets a real multi-line details editor and a size limit message\n\nThe feedback form keeps your typed details after submit or Ctrl-C and warns before you exceed the size cap.\n\n**What**\n\nThe details field in the feedback form is now a proper multi-line editor that keeps your text after submit and survives Ctrl-C, and it tells you when an edit would exceed the size cap instead of silently truncating.\n\n**Details**\n\n- The shared text input now forwards `disableBackslashReturn`, `clearOnSubmit` and `disableCtrlCClear` down to the underlying editor.\n- The feedback details field sets these so it does not clear on submit and Ctrl-C does not wipe what you typed.\n- Editing past the details cap produces a message asking you to trim first; the KB figure quoted in that message is computed at runtime rather than hardcoded.\n\n**Evidence**\n\n`That edit would push Details past the`\n\n- Area: Feedback Form\n- Names: `\/bug`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 0\/5"}