From 8d10fa1f2d2d26cfb5ca5bcbee0bd6d0f77b730a Mon Sep 17 00:00:00 2001 From: James Graham Date: Wed, 29 Apr 2015 19:49:38 +0100 Subject: Add basic support for executeAsyncScript. This relies on a global webdriverCallback function, which is visible to content. Obviously that's not a long term solution for a number of reasons, but it allows us to experiment for now --- components/script/script_task.rs | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) (limited to 'components/script/script_task.rs') diff --git a/components/script/script_task.rs b/components/script/script_task.rs index df838f130e8..b114819c613 100644 --- a/components/script/script_task.rs +++ b/components/script/script_task.rs @@ -316,7 +316,7 @@ pub struct ScriptTask { /// The JavaScript runtime. js_runtime: Rc, - mouse_over_targets: DOMRefCell>> + mouse_over_targets: DOMRefCell>>, } /// In the event of task failure, all data on the stack runs its destructor. However, there @@ -814,7 +814,9 @@ impl ScriptTask { WebDriverScriptCommand::GetElementText(node_id, reply) => webdriver_handlers::handle_get_text(&page, pipeline_id, node_id, reply), WebDriverScriptCommand::GetTitle(reply) => - webdriver_handlers::handle_get_title(&page, pipeline_id, reply) + webdriver_handlers::handle_get_title(&page, pipeline_id, reply), + WebDriverScriptCommand::ExecuteAsyncScript(script, reply) => + webdriver_handlers::handle_execute_async_script(&page, pipeline_id, script, reply), } } -- cgit v1.2.3