We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
@garris do you think this is something that would belong in master or do you expect this type of functionality to exist in the consumer's space?
danDanV1@2ca1b82
scenario.scrollToSelector uses scrollIntoView() under the hood, and sometimes you need use the options supported by scrollIntoView()
scenario.scrollToSelector
scrollIntoView()
eg.
element.scrollIntoView({ block: "end", inline: "end" });
Implementation
const options = { scenario: { scrollToSelector: "#myid", scrollIntoViewOptions: { block: "end", inline: "end" } } } await backstop(assert, options);
It's a pity that in the scenario option in backstopjs itself is called scrollToSelector because it's not calling window.scrollTo.
scrollToSelector
window.scrollTo
Something like this would have clearer semantics:
{ scenario: { scrollIntoView: { selector: "#myid", options: { block: "end", inline: "end" } } } }
but that'd be a breaking change in the scenario settings...
The text was updated successfully, but these errors were encountered:
No branches or pull requests
@garris do you think this is something that would belong in master or do you expect this type of functionality to exist in the consumer's space?
danDanV1@2ca1b82
scenario.scrollToSelector
usesscrollIntoView()
under the hood, and sometimes you need use the options supported byscrollIntoView()
eg.
Implementation
It's a pity that in the scenario option in backstopjs itself is called
scrollToSelector
because it's not callingwindow.scrollTo
.Something like this would have clearer semantics:
but that'd be a breaking change in the scenario settings...
The text was updated successfully, but these errors were encountered: