convert javascript snippets to standalone embedded js files (part 1) #852
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.
The purpose is to make it easy to maintain the js source code.
This PR contains three parts:
dom.ScrollIntoViewIfNeeded()
to replace the js implementationparseRemoteObject
function and improve the docCallFunctionOn
and refactor the poll action to use the this funcEvaluate
withCallFunctionOn
to execuate js on node. Pros and cons:CallFunctionOn
needs 3 commands to execute js on a node (whileEvaluate
just needs one):DOM.resolveNode
Runtime.callFunctionOn
Runtime.releaseObject
.move js function into standalone js files and load them with//go:embed
//go:embed
is a new feature in go 1.16, so we should put this PR on hold until we decide to drop support for go 1.15 (maybe when go 1.17 is released?).Maybe it's better to split this PR into 3 PRs.Update: We will split it into 2 PRs. Item 1 and item 2 will be released first. Item 3 will be put into another PR and it's planed to be released once go 1.17 is released.