The feedback form keeps your typed details after submit or Ctrl-C and warns before you exceed the size cap.
What's wrong with this entry?
The 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.
- The shared text input now forwards
disableBackslashReturn,clearOnSubmitanddisableCtrlCCleardown to the underlying editor. - The feedback details field sets these so it does not clear on submit and Ctrl-C does not wipe what you typed.
- 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.
That edit would push Details past the
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.234
Survey follow-ups carry their context into /feedback for 30 seconds
Both mention feedback
-
v2.1.235
Bug reports are trimmed to fit an 8 MiB upload limit
Both mention feedback
-
v2.1.235
Bug reports that are too large drop the transcript automatically
Both mention feedback