We used to have somewhat defective mechanism for the tests running in the extension context to invoke some selected methods on the front-end. Over the time the need evolved for a more generic mechanism similar to the way it's done from the tested page. This switches all methods that used to rely on dispatchOnFrontend() to evaluateOnFrontend(), also moves some of the less-used methods from extensions-test.js to particular test files that need them.
Created attachment 98205 [details] patch
Comment on attachment 98205 [details] patch View in context: https://bugs.webkit.org/attachment.cgi?id=98205&action=review > LayoutTests/http/tests/inspector/extensions-test.js:25 > + var reply = InspectorTest._replyToExtension.bind(null, event.ports[0]); Please add a comment that this variable may be used by the eval'ed code.
Manually committed r89656: http://trac.webkit.org/changeset/89656