[GTK] Wrong transfer annotations used in GObject DOM bindings
authorcarlosgc@webkit.org <carlosgc@webkit.org@268f45cc-cd09-0410-ab3c-d52691b4dbfc>
Tue, 17 Mar 2015 12:22:06 +0000 (12:22 +0000)
committercarlosgc@webkit.org <carlosgc@webkit.org@268f45cc-cd09-0410-ab3c-d52691b4dbfc>
Tue, 17 Mar 2015 12:22:06 +0000 (12:22 +0000)
commit81ad6de23a5db7b298df5cfac977bafdc30366a6
treec1b4052a9727e00a6744334a12cd754dbefb06e6
parentc30b6ad78db9f5187009bd49102803391e46c944
[GTK] Wrong transfer annotations used in GObject DOM bindings
https://bugs.webkit.org/show_bug.cgi?id=142780

Reviewed by Gustavo Noronha Silva.

We are using transfer none for all methods returning a GObject DOM
Object. That's not true. Only objects derived from Node are
automatically released by the DOM object cache and can be transfer
none. All other objects are added to the cache only to avoid
creating the same wrapper twice for the same core object, but
caller should release the returned reference.

* bindings/gobject/WebKitDOMCustomUnstable.h:
* bindings/scripts/CodeGeneratorGObject.pm:
(GetTransferTypeForReturnType):
(GenerateFunction):

git-svn-id: https://svn.webkit.org/repository/webkit/trunk@181643 268f45cc-cd09-0410-ab3c-d52691b4dbfc
Source/WebCore/ChangeLog
Source/WebCore/bindings/gobject/WebKitDOMCustomUnstable.h
Source/WebCore/bindings/scripts/CodeGeneratorGObject.pm