On Nov 13, 2012, at 10:44 AM, Joshua Bell <jsb...@chromium.org> wrote:
> The switch from DOMException of type TYPE_MISMATCH_ERR to TypeError does not > appear to be controversial, but as arv@ mentioned in one of the bugs: > > "WebIDL only defines bindings for ECMAScript. We really need someone from > Apple to take care of the ObjC bindings, someone from QT for CPP bindings and > someone for GTK to take care of the GTK bindings." > > And by "take care of" we mean "define what a WebIDL TypeError even means in > binding XYZ". So - help appreciated. It seems to me that translating TypeError into TYPE_MISMATCH_ERR in each of those bindings would be an acceptable stopgap while we investigate “what TypeError event means” for that binding and would get rid of the mechanical problem of having to do this all at once. -- Darin _______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev
