Add support for in-page links in ChromeVox.

chrome/common/extensions/api/automation.idl

 // Copyright 2014 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.
 
 // The <code>chrome.automation</code> API allows developers to access the
 // automation (accessibility) tree for the browser. The tree resembles the DOM
 // tree, but only exposes the <em>semantic</em> structure of a page. It can be
 // used to programmatically interact with a page by examining names, roles, and
 // states, listening for events, and performing actions on nodes.
 [nocompile] namespace automation {
@@ skipping 424 matching lines @@
 
     // The nodes, if any, which form a label for this element. Generally, the
     // text from these elements will also be exposed as the element's accessible
     // name, via the $(ref:automation.AutomationNode.name) attribute.
     AutomationNode[]? labelledBy;
 
     // The node referred to by <code>aria-activedescendant</code>, where
     // applicable
     AutomationNode? activeDescendant;
 
+    // The target of an in page link.
+    AutomationNode? inPageLinkTarget;
+
     //
     // Link attributes.
     //
 
     // The URL that this link will navigate to.
     DOMString? url;
 
     //
     // Document attributes.
     //
@@ skipping 329 matching lines @@
     // Everything in the tree between the two node/offset pairs gets included
     // in the selection. The anchor is where the user started the selection,
     // while the focus is the point at which the selection gets extended
     // e.g. when dragging with a mouse or using the keyboard. For nodes with
     // the role staticText, the offset gives the character offset within
     // the value where the selection starts or ends, respectively.
     [nocompile] static void setDocumentSelection(
         SetDocumentSelectionParams params);
   };
 };