-
Notifications
You must be signed in to change notification settings - Fork 135
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
question about gif format #84
Comments
used FileReader instead of Image. and now it works :) you can close this issue. |
We do not support gifs in our Image wrapper currently. There are various reasons for this, but mainly because requirement for this seems to be very rare :) |
I vote for this. Need gif support to embed image thumbnails, going to be uploaded with plupload. |
What do you think we should do with animated gifs (having in mind that people might expect Plupload to resize them on client-side as well)? |
Good point. The basic version could only render the first frame of the GIF. While I'm using moxie image for embedded preview thumbnails in a Plupload queue, this would be OK for my use case. Although it is possible to scale an animated GIF (including all frames) with software like ImageMagick, I don't now if there is a relatively easy way to accomplish this with pure JavaScript. |
Hi,
thanks for the awesome open source, it literally helped me a lot :)
I'm trying to make a preview image viewer, before uploading with plupload.
followed this code.
source :
http://www.bennadel.com/blog/2563-showing-plupload-image-previews-using-base64-encoded-data-urls.htm
In here, this works fine, if the upload file is png, or jpg format.
but it doesn't work, when the format is gif format :(
gif format is not supported? or is the code bug?
in here,
https://github.com/moxiecode/moxie/wiki/Image#getAsDataURL-typeimagejpegquality90-method
it says,
[type="image/jpeg"] String
Mime type of resulting blob. Can either be image/jpeg or image/png
so it means gif is not supported?
I'll be waiting for response
Thank you!
The text was updated successfully, but these errors were encountered: