Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Actions on Every Element #16

Open
tbostic32 opened this issue Nov 16, 2020 · 0 comments
Open

Actions on Every Element #16

tbostic32 opened this issue Nov 16, 2020 · 0 comments

Comments

@tbostic32
Copy link
Collaborator

As we have continued to test on real site, I have found myself continually relaxing the restraints on what is considered for an element to be interactable. We had pretty hard criteria (still mostly do), but I am now starting to automatically allow links to have mouseover events because of running into https://coag.gov/ where we need that to explore the dropdowns.

So the question is, at what point do we just start trying actions on every element on the page that we can see. In the example above, there is no reason that those couldn't be div elements or something else and our current solution would fail. The two big downsides I see are:

  1. Runtime - Trying all of these actions, especially if they create a lot more edges, could increase runtime significantly.
  2. Global Listeners - Similar to 1, but we have seen carousels that move no matter where you are on the page, with trying everything we would significantly multiply the number of times we interact with the carousel (or whatever global object).

The positive would be that we can be more sure of actually creating a full graph and not missing any content.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant