RESOLVED INVALID 40964
JSC bindings for Image Resizer API (recreated due to commit-queue bug)
https://bugs.webkit.org/show_bug.cgi?id=40964
Summary JSC bindings for Image Resizer API (recreated due to commit-queue bug)
Sterling Swigart
Reported 2010-06-21 19:28:29 PDT
This patch exposes the classes and their callbacks to JSC through Image.webkitGetImage. The API is functionally incomplete, so it only will ever call the error callback or throw exceptions. Recreated from 40854: (In reply to comment #5) > (From update of attachment 59165 [details]) > I'm pretty sure you can create these bindings without any extra code. If you have trouble, you should ask dumi. > Done. > WebCore/ChangeLog:59 > + 2010-06-18 Sterling Swigart <sswigart@google.com> > You have two ChangeLogs in this patch. > Extras deleted, ChangeLogs recreated anyway. > WebCore/bindings/js/JSCustomImageResizerErrorCallback.cpp:47 > + JSCustomImageResizerErrorCallback::JSCustomImageResizerErrorCallback(JSObject* callback, JSDOMGlobalObject* globalObject) > We should be able to auto-generate these callbacks now. There are some examples in the database bindings. > Done; I changed CodeGenerator.pm to allow for this. > WebCore/html/HTMLImageElement.idl:56 > + [Custom] void webkitGetImage(in DOMString mimeType, in ImageResizerSuccessCallback successCallback, [Optional] in ImageResizerErrorCallback errorCallback, [Optional] in ResizeOptions options) > This shouldn't be custom. This is currently in discussion, but I'm still looking for further feedback regarding this patch.
Attachments
Patch 2: JSC bindings (95.48 KB, patch)
2010-06-21 19:29 PDT, Sterling Swigart
no flags
Sterling Swigart
Comment 1 2010-06-21 19:29:52 PDT
Created attachment 59325 [details] Patch 2: JSC bindings
Sterling Swigart
Comment 2 2010-06-21 19:38:17 PDT
My patches are still failing with no explanation. . . .
Sterling Swigart
Comment 3 2010-06-24 15:23:34 PDT
This bug was an attempt to trick the buildbot into giving me reasons for the failures. It did not work, however, so I am invalidating the bug.
Note You need to log in before you can comment on or make changes to this bug.