I'm not sure this is a bug or intentional, but I just noticed this behavior with setting file size upload limits and using App Connect's Image Resize Options together. This is on v6.8.0 so I can't test this on v7x.
- If I set a file size upload limit on an input type="file", the validation is enforced.
- If I set a max width or max height on an input type="file" and that file is an image, the resizing works on the client before upload.
- If I set both file size upload limit & a Image Resize Option, the image resize option is applied first, then the upload limit validation is checked.
Since many UI's with file uploads state a max file size for uploads, (and doesn't mention the image will be resized as well), I find Wappler's order of execution odd or backwards. If my UI says "1MB max" below the file input field, this tells users don't pick a file larger than 1MB. However, if my page is also using Image Resize Options, those settings could mean the user could pick a 1.5MB file for upload without the validation throwing an error (because after resize, it may be smaller than 1MB). This makes the UI look incorrect.
The purpose of stating a max file size in the UI is to give guidance about the largest file to start with. When Image Resize Options are applied first, the max file size becomes guidance for where the file ends up after resize. Since the user has no idea a resize is happening, they interpret the UI as mislabled or actually lacking the file size limit.
Thoughts?