On 2013/06/14 12:45, Jonas Sicking wrote:
> Wouldn't an even better solution be to make browsers support that EXIF
> metadata and simply render the image correctly without any action from
> the page? At least assuming that the EXIF metadata for orientation is
> standardized and implemented consiste
On Thu, Jun 13, 2013 at 8:06 PM, Mark Callow wrote:
> On 2013/06/08 5:42, David Flanagan wrote:
>
>
> [A related, but perhaps too ambitious, proposal is to allow direct
> read/write access to EXIF metadata via HTMLImageElement. The primary use
> case for read access is to enable web apps to trivi
On 2013/06/08 5:42, David Flanagan wrote:
>
> [A related, but perhaps too ambitious, proposal is to allow direct
> read/write access to EXIF metadata via HTMLImageElement. The primary
> use case for read access is to enable web apps to trivially determine
> when, where, and how a photo was taken a
We have a JS API for that in Wakanda
http://doc.wakanda.org/Images/Image-Class/meta.303-660131.en.html
It use the saveMeta() meta method to apply potential changes:
http://doc.wakanda.org/Images/Image-Class/saveMeta.301-661057.en.html
It was implemented a bit fast but it does correctly the job fo
On Fri, Jun 7, 2013 at 1:42 PM, David Flanagan wrote:
> If the second argument to Canvas.toBlob() and Canvas.toBlobHD() is
> "image/jpeg", then these methods support a third argument to specify JPEG
> compression level.
>
> The spec
> (http://www.whatwg.org/specs/web-apps/current-work/multipage/th
If the second argument to Canvas.toBlob() and Canvas.toBlobHD() is
"image/jpeg", then these methods support a third argument to specify
JPEG compression level.
The spec
(http://www.whatwg.org/specs/web-apps/current-work/multipage/the-canvas-element.html#a-serialization-of-the-bitmap-as-a-file)
