Bug 127651 – [GTK] Web Inspector doesn't work with network process enabled

• Status: RESOLVED
• Resolution: FIXED
• Component: WebKit2

[Carlos Garcia Campos]

Nothing happens when inspecting an element in MiniBrowser and unit tests time out.

../../Tools/Scripts/run-gtk-tests --verbose --no-xvfb Programs/TestWebKitAPI/WebKit2Gtk/TestInspector***
TEST: Programs/TestWebKitAPI/WebKit2Gtk/TestInspector... (pid=7928)
  /webkit2/WebKitWebInspector/default:                                 OK
  /webkit2/WebKitWebInspector/manual-attach-detach:                    OK
  /webkit2/WebKitWebInspector/custom-container-destroyed:              OK
PASS: Programs/TestWebKitAPI/WebKit2Gtk/TestInspector

$ WEBKIT_USE_NETWORK_PROCESS=1 ../../Tools/Scripts/run-gtk-tests --verbose --no-xvfb Programs/TestWebKitAPI/WebKit2Gtk/TestInspector
TEST: Programs/TestWebKitAPI/WebKit2Gtk/TestInspector... (pid=7832)
  /webkit2/WebKitWebInspector/default:                                 OK
TEST: Programs/TestWebKitAPI/WebKit2Gtk/TestInspector: TIMEOUT

[Carlos Garcia Campos]

It doesn't always happen, sometimes it works perfectly so it looks like a race condition somewhere. I've debugged this for a while and I've noticed that when it doesn't work some resources are not loaded, for example InspectorJSBackendCommands.js and InspectorWebBackendCommands.js. Those are inserted in the document by LoadInspectorBackendCommands.js which is always loaded.

[Carlos Garcia Campos]

Created attachment 225351 [details]
Patch

[Sergio Villar Senin]

Comment on attachment 225351 [details]
Patch

Awesome find!

[Carlos Garcia Campos]

Committed r164787: <http://trac.webkit.org/changeset/164787>