[chromedriver]Implement command: title.

chrome/test/chromedriver/commands.cc

 // Copyright (c) 2012 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 #include "chrome/test/chromedriver/commands.h"
 
 #include "base/bind.h"
 #include "base/callback.h"
 #include "base/file_util.h"
 #include "base/format_macros.h"
@@ skipping 87 matching lines @@
   std::string script;
   if (!params.GetString("script", &script))
     return Status(kUnknownError, "'script' must be a string");
   const base::ListValue* args;
   if (!params.GetList("args", &args))
     return Status(kUnknownError, "'args' must be a list");
 
   return session->chrome->CallFunction(
       "function(){" + script + "}", *args, value);
 }
+
+Status ExecuteTitle(
+    Session* session,
+    const base::DictionaryValue& params,
+    scoped_ptr<base::Value>* value) {
+  base::ListValue args;
+  return session->chrome->CallFunction(
+      "function(){ return document.title; }", args, value);

[kkania, 2013/01/04 04:35:34]

see how the old chromedriver does it webdriver::Session::GetTitle; you might
want to follow the same approach; i think the idea is to return the title as the
user would see it

[chrisgao (Use stgao instead), 2013/01/05 01:19:09]

Followed the approach of the old chromedriver.

But when attribute <title> is NOT specified. For different urls, the user will
see different titles:
1. file://some/path/file_name.html
  "file_name.html" shows in tab title.
2. https://some.hostname
  "https://some.hostname" shows up.
3. http://some.hostname
  Only "some.hostname" shows up.

Do you think we should deal with different types of protocols in the url?

+}