From c78d4bfe7cae7156759aaaea2900a6488940e489 Mon Sep 17 00:00:00 2001 From: Mikael Finstad Date: Wed, 10 Aug 2022 10:50:35 +0200 Subject: [PATCH] Fix statement about cropping images in README.md (#3964) --- README.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index e1e610d344..55fa4238b7 100644 --- a/README.md +++ b/README.md @@ -194,7 +194,8 @@ bundle, so no need to include anything additionally: Having no JavaScript beats having a lot of it, so that’s a fair question! Running an uploading & encoding business for ten years though we found that in cases, the file input leaves some to be desired: * We received complaints about broken uploads and found that resumable uploads are important, especially for big files and to be inclusive towards people on poorer connections (we also launched [tus.io](https://tus.io) to attack that problem). Uppy uploads can survive network outages and browser crashes or accidental navigate-aways. -* Uppy supports editing meta information before uploading (such as cropping of images). +* Uppy supports editing meta information before uploading. +* Uppy allows cropping images before uploading. * There’s the situation where people are using their mobile devices and want to upload on the go, but they have their picture on Instagram, files in Dropbox or a plain file URL from anywhere on the open web. Uppy allows to pick files from those and push it to the destination without downloading it to your mobile device first. * Accurate upload progress reporting is an issue on many platforms. * Some file validation — size, type, number of files — can be done on the client with Uppy.