Bug 21009 – [PATCH] webkit_web_view_execute_script returning an execution result value

• Component: WebKitGTK
• Status: RESOLVED WONTFIX

[Anton Nonko]

This patch makes webkit_web_view_execute_script function to return an execution result value. The value is returned as an UTF8 string like in other bindings. The return value is a pointer to gchar null-terminated string or NULL if error occurred. This pointer is actual before the next call of webkit_web_view_execute_script for same WebKitWebView object or object finalizing.
Calling code should not release pointer returned.

[Anton Nonko]

Created attachment 23675 [details]
webkit_web_view_execute_script returning result of execution

[Alp Toker]

Comment on attachment 23675 [details]
webkit_web_view_execute_script returning result of execution

Antonin,

webkit_web_view_execute_script() was intended for very simple uses only. For anyone needing return values, it's probably more appropriate to use the JavaScriptCore API directly or use the gjs GObject/JavaScript bridge (developed externally to WebKit at the moment).

Even if we have to add a new convenience function like this, I'd prefer not to change webkit_web_view_execute_script() but add a new function clearly named for the purpose.

If you're interested in further JavaScript integration in the API, you could investigate what it would take to get gjs merged into WebKit so we can do more integration.

Marking r- because at the very least this will need a new function (along with documentation). Would be interested to hear the thoughts of others on this.

[Anton Nonko]

This change as a full analogue of runScript() method of wxWebView class in wx port. It's still very simple and doesn't affect existing user code.

I consider that the best way is using gjs but exactly for very simple cases it may be useful.

[Martin Robinson]

Going to close this as the WebKit 1 API has been removed for quite some time.