Introducing improvements for the Action Recorder Extension.
1. Improved the xpath generator. The generator will produce even more concise xpaths. This improvement helps to make test recipes readable to humans. 2. Changed the way the extension queries for an iframe's context. Prior to this change, the extension would construct a path from the iframe to the top level frame by making a query at each ancestor frame node. However, InProcessBrowserTest does not need a path to go from the top level frame to a descendant iframe. Therefore, in this change the extension only makes one query at the parent frame node. 3. Moved the frame context query action to the front of the start recording workflow. This move cuts one message roundtrip from the extension's background script to the extension's content script. 4. Made the extension jot down a target element's visibility state when recording an action. Prior to this change, the extension assumes that every target element is visible, enabled and on the top of the page. However, the extension's complex action recording logic sometimes catches actions on invisible or partially obscured elements. 5. Added refined logic to the extension to distinguish between a user typing action and a Chrome autofill action. Prior to this change the extension simply assumes that Chrome always autofills every autofill-able field. If a user types inside an autofillable field, the extension will mistakenly record an autofill action. With this change the extension uses keyboard events to detect when a user types inside a field, eliminating the false positive. 6. Began implementing new features to capture Chrome Password Manager actions. Bug: 855284 Change-Id: Ic7ff3af95cdc9f308c3ad061a3506fced150b4f8 Reviewed-on: https://chromium-review.googlesource.com/1132540 Commit-Queue: Yiming Zhou <uwyiming@google.com> Reviewed-by:Jared Saul <jsaul@google.com> Reviewed-by:
Mathieu Perreault <mathp@chromium.org> Cr-Commit-Position: refs/heads/master@{#574385}
Showing
Please register or sign in to comment