However, the returned path
attribute of the PickedFile
points to a network
resource, and not a local path in your users' drive. See Use the plugin below for some examples on how to use this return value in a cross-platform way.
In order to filter only video/image content, some browsers offer an accept
attribute in their input type="file"
form elements:
This feature is just a convenience for users, not validation.
Users can override this setting on their browsers. You must validate in your app (or server) that the user has picked the file type that you can handle.
In order to “take a photo”, some mobile browsers offer a capture
attribute:
Each browser may implement capture
any way they please, so it may (or may not) make a difference in your users' experience.
The arguments maxWidth
, maxHeight
and imageQuality
are not supported on the web.
The argument maxDuration
is not supported on the web.
This package is an unendorsed web platform implementation of image_picker
.
In order to use this, you'll need to depend in image_picker: ^0.6.7
(which was the first version of the plugin that allowed federation), and image_picker_for_web: ^0.1.0
.
... dependencies: ... image_picker: ^0.6.7 image_picker_for_web: ^0.1.0 ... ...
You should be able to use package:image_picker
almost as normal.
Once the user has picked a file, the returned PickedFile
instance will contain a network
-accessible URL (pointing to a location within the browser).
The instace will also let you retrieve the bytes of the selected file across all platforms.
If you want to use the path directly, your code would need look like this:
... if (kIsWeb) { Image.network(pickedFile.path); } else { Image.file(File(pickedFile.path)); } ...
Or, using bytes:
... Image.memory(await pickedFile.readAsBytes()) ...