[EXPERIMENTAL] feature(webpage-impact): add support for custom user interactions #30
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
alexzurbonsen
force-pushed
the
add-support-for-custom-user-interactions
branch
2 times, most recently
from
a550a86
to
8755661
Compare
Signed-off-by: alexzurbonsen <[email protected]>
alexzurbonsen
force-pushed
the
add-support-for-custom-user-interactions
branch
from
8755661
to
3c0e337
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Context
It would be nice to interact with the page in a custom way, depending on the webpage that is loaded. E.g. click on cookie banners, login etc.
Summary
Enable execution of custom user provided scripts on the loaded page.
Caveats:
dataReloadRatiois unreliable with the current change, since the script is only executed on first load. One could change that easily. How to deal with non idempotent actions like logins then? I guess one could require the user to deal with that and check if he is already logged in, for example. But is it that easy in every case?