member badge
Arunkumar Kumaresan
Issue:
When uploading a large file in the article editor, the UI gives no feedback during upload — the screen appears idle with no progress indicator. The user only discovers the upload failed after waiting, when an error toast appears: "Failed to read the request form. Request body too large. The max request body size is 157286400 bytes."
Problems with current behavior:
  1. No progress indicator or spinner during upload, so users can't tell if anything is happening.
  2. No upfront indication of the max file size (150 MB) before the user selects/attaches a file, failure is discovered only after the wait.
  3. The error message exposes a raw byte value (157286400 bytes) instead of a human-readable size (150 MB), which is confusing for non-technical users.
Suggested fix:
  1. Validate file size client-side before upload starts, and reject immediately with a clear message (e.g., "File exceeds the 150 MB upload limit. Please upload a smaller file.").
  2. Display the max upload size limit near the upload/attach control proactively.
  3. Show a progress bar or loading state during upload so users know the action is in progress.
  4. Convert any byte-based limits in error messages to human-readable units (KB/MB/GB).
Impact: Users waste time waiting on uploads that are destined to fail, and the technical error message creates confusion and support tickets.

Photo Viewer

View photos in a modal