Widget 2.8.2

widget April 04, 2016

Preview for video captured from the camera or picked from local files.

Preview for images captured from the camera is displayed before uploading.

See it in action. You can find full changelog entry here

Widget 2.8.0. Video capture

widget March 14, 2016

Now your users can capture video right from the camera tab if a browser is capable (Firefox and latest Google Chrome at the moment).

We've switched from YUI Compressor to UglifyJS and CSSO. The size of minified library is reduced by 15%, gzipped size by 8%.

CommonJS compatibility added. This allows you to use the widget in NodeJS, Browserify and Webpack environments.

New library builds were added (in addition to uploadcare and uploadcare.all):

  • uploadcare.api — without jQuery and UI. Only upload API client.
  • uploadcare.lang.en — stripped localization to reduce the size, only English is included.
  • uploadcare.ie8 — with jQuery 1.12.1 (IE8 does not work with jQuery 2+).

See it in action. You can find full changelog entry here

Widget 2.7.0

widget March 10, 2016
  • Camera tab is disabled on non HTTPS sites due to the latest browsers' rules.
  • The widget constructors raise errors if no elements ware matched for provided selector and prints warning if more than one element is matched.
  • Built-in jQuery upgraded to 2.2.1.
  • File's MIME type is exposed to Javascript info.

See it in action. You can find full changelog entry here.

Widget 2.6.0

widget January 09, 2016

Image crop and preview for most files are significantly faster in this update. Previously all files were uploaded to the server and appropriately resized versions were downloaded from CDN for preview. This meant that the user was forced to wait during file uploading, image resizing and delivery over the network.

Starting from version 2.6.0 the widget attempts to render local files as images using HTML5 APIs. This gives the ability to deliver, crop and preview immediately. Of course, browsers are not able to open all image formats which our servers are. In the case files can't be rendered on the client side, they will be handled in the old way.

This significantly speeds things up when possible (vastly improving UX) but will not affect other cases.

You can find full changelog entry here

Cookies on Uploadcare

We have placed cookies on your device to improve your experience.  Learn more about how this site works and our compliances