Skip to content

fix: More explicit error message when DOM selector is invalid #109

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

Merged
merged 1 commit into from
Sep 22, 2015

Conversation

pixelastic
Copy link
Contributor

Fixes #105

@@ -1,13 +1,21 @@
function getContainerNode(selectorOrHTMLElement) {
if (typeof selectorOrHTMLElement === 'string') {
return document.querySelector(selectorOrHTMLElement);
var isFromString = (typeof selectorOrHTMLElement === 'string');
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there a need for parenthesis here?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems they are not needed indeed

@vvo
Copy link
Contributor

vvo commented Sep 22, 2015

Great, only waiting for comment on (type of)

@pixelastic
Copy link
Contributor Author

They might not be needed, but I feel they improve readability.

@vvo
Copy link
Contributor

vvo commented Sep 22, 2015

They might not be needed, but I feel they improve readability.

Ok no preference here

@vvo vvo assigned Jerska and pixelastic and unassigned Jerska Sep 22, 2015
@vvo
Copy link
Contributor

vvo commented Sep 22, 2015

LGTM

pixelastic added a commit that referenced this pull request Sep 22, 2015
fix: More explicit error message when DOM selector is invalid
@pixelastic pixelastic merged commit 5ebfe75 into develop Sep 22, 2015
@vvo vvo deleted the fix/get-container-node-error branch September 22, 2015 11:38
aymeric-giraudet pushed a commit that referenced this pull request Dec 8, 2022
sarahdayan pushed a commit that referenced this pull request Dec 12, 2022
When you click these buttons in latest Chrome, it will keep those buttons on the same place in the viewport, which means that users will skip the next page of results. With this property added, that's fixed.

This solution comes from https://bugs.chromium.org/p/chromium/issues/detail?id=1110323#c1 and has been verified by three customers so far.
sarahdayan pushed a commit that referenced this pull request Dec 14, 2022
When you click these buttons in latest Chrome, it will keep those buttons on the same place in the viewport, which means that users will skip the next page of results. With this property added, that's fixed.

This solution comes from https://bugs.chromium.org/p/chromium/issues/detail?id=1110323#c1 and has been verified by three customers so far.
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

Successfully merging this pull request may close these issues.

3 participants