google / automation-inspector Goto Github PK

Support boundsForRange, setSelection and other functions that require parameters.

Getting ReferenceError: ids is not defined after downloading the extension and click the extension icon when viewing a webpage.

The error trace is not very helpful...
Guessing an investigation need to be made.

Chrome Version: 77.0.3847.0 (Official Build) canary (64-bit)
System Version: macOS 10.14.5 (18F132)

Ability to pick an item with the mouse.

There's a hitTest function in automationNode that can be used.

There can be a lot of noisy mutations in the page.

It might be nice to limit event groups to those only from keyboard usage.

Currently we highlight what properties were changed in a nodeChanged notification.

However, we are only able to do this if the node was previously displayed in the DOM tree -- otherwise we don't know what the original properties were.

It might be nice if the nodeChanged notification passed this info to us.

A slug is something like p#para1

This is useful for understanding where the current node is in the tree. It's probably a good idea to expose this somewhere in the UI. Maybe it could be a property.

Make it work with a screen reader.

Example accessible treegrid:
https://rawgit.com/w3c/aria-practices/treegrid/examples/treegrid/treegrid-1.html

Depends on Fancytree work here:
mar10/fancytree#709

In app mode for Chrome OS, viewing the entire desktop tree along with all events provides an overwhelming ream of data.

We should prompt the user for a window that they wish to inspect.

Allow one Automation Inspector on one computer to inspect Chrome on a different computer.

This would have a big benefit in that focus would remain in the inspected app, instead of moving back and forth between the app and inspector, which can have big side effects.

Draw a rectangle around the current item.

We will need to create a chrome highlight api that will set an attribute such as
automation-api-highlight=true

Then we can inject css with a rule like *[automation-api-highlight=true] { outline: 3px solid #f00 !important; }

AutomationNode instances already have an internal id. These would be useful to have instead of generating our own id. It could also be useful for debugging Chrome.

Let's just expose and consume these.

Steps:

1. Open a document with an iframe
2. Inspect

Notice that the contents of the iframe are not shown in the inspector tree view.

Hi @aleventhal
Very new to this extension, please forgive me if I missed something obvious.

Followed the "Running from the local file system" section from
https://github.com/google/automation-inspector/blob/master/README.md

Using developer mode from the Chrome extensions page at chrome://extensions, use the load unpacked extension feature, pointing it at the build/extension folder.

Unfortuently getting 404 for /third_party/*.js
(e.g., chrome-extension://enlmgkkaebjkhjbeajabgddgmggdeadf/third_party/jquery.fancytree.table.js)

A quick guess is something wrong with the Gruntfile.js, not sure right now though.
Happy to dig into it sometime late this week(maybe it's just a mistake I made 😅).

And ideas? Thanks!

This is because automationNode.querySelectorAll() doesn't exist. Only querySelector() is available.

I started a patch to work on this for Chrome, but it was hard because WebNode also didn't have querySelectorAll(), nor was there a concept of a static node list in the public web APIs.

We should allow for panel resizing. Should work with the keyboard ala https://codepen.io/rstrahl/pen/eJZQej

The JSON syntax is easy to forget. We should allow users to say what roles, states, etc. they are interested in filtering for.