Mixing
"Element is not clickable at point” New Relic [duplicate]
This question already has an answer here:
Selenium Web Driver & Java. Element is not clickable at point (x, y). Other element would receive the click
5 answers
I am having some struggle with my Selenium JS in New relic. I am trying to click an element and I am keeping get back the error "Element is not clickable at point". The solutions at the tread Selenium Web Driver & Java. Element is not clickable at point (x, y). Other element would receive the click are not really applicable to NewRelic.
The snippet I am using is
.then(function() {
log(26, 'clickElement "//form[@id='giftcard-form']/div[3]/div/button"');
return $browser.waitForAndFindElement(By.xpath("//form[@id='giftcard-form']/div[3]/div/button"), DefaultTimeout); })
.then(function (el) { el.click(); })
I don't see anything wrong with the code and the element is visible on the page.
![enter image description here][1]
Any suggestions? it seems a common issue but I didn't have luck with the solutions offered in the other thread
Thanks,
Thomas
javascript selenium selenium-webdriver newrelic
asked Nov 19 '18 at 20:27
Samoht RusconiSamoht Rusconi
104
marked as duplicate by DebanjanB selenium
Users with the selenium badge can single-handedly close selenium questions as duplicates and reopen them as needed.
StackExchange.ready(function() {
if (StackExchange.options.isMobile) return;
$('.dupe-hammer-message-hover:not(.hover-bound)').each(function() {
var $hover = $(this).addClass('hover-bound'),
$msg = $hover.siblings('.dupe-hammer-message');
$hover.hover(
function() {
$hover.showInfoMessage('', {
messageElement: $msg.clone().show(),
transient: false,
position: { my: 'bottom left', at: 'top center', offsetTop: -7 },
dismissable: false,
relativeToBody: true
});
},
function() {
StackExchange.helpers.removeMessages();
}
);
});
});
Nov 19 '18 at 21:26
This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.
add a comment |
This question already has an answer here:
Selenium Web Driver & Java. Element is not clickable at point (x, y). Other element would receive the click
5 answers
I am having some struggle with my Selenium JS in New relic. I am trying to click an element and I am keeping get back the error "Element is not clickable at point". The solutions at the tread Selenium Web Driver & Java. Element is not clickable at point (x, y). Other element would receive the click are not really applicable to NewRelic.
The snippet I am using is
.then(function() {
log(26, 'clickElement "//form[@id='giftcard-form']/div[3]/div/button"');
return $browser.waitForAndFindElement(By.xpath("//form[@id='giftcard-form']/div[3]/div/button"), DefaultTimeout); })
.then(function (el) { el.click(); })
I don't see anything wrong with the code and the element is visible on the page.
![enter image description here][1]
Any suggestions? it seems a common issue but I didn't have luck with the solutions offered in the other thread
Thanks,
Thomas
javascript selenium selenium-webdriver newrelic
asked Nov 19 '18 at 20:27
Samoht RusconiSamoht Rusconi
104
marked as duplicate by DebanjanB selenium
Users with the selenium badge can single-handedly close selenium questions as duplicates and reopen them as needed.
StackExchange.ready(function() {
if (StackExchange.options.isMobile) return;
$('.dupe-hammer-message-hover:not(.hover-bound)').each(function() {
var $hover = $(this).addClass('hover-bound'),
$msg = $hover.siblings('.dupe-hammer-message');
$hover.hover(
function() {
$hover.showInfoMessage('', {
messageElement: $msg.clone().show(),
transient: false,
position: { my: 'bottom left', at: 'top center', offsetTop: -7 },
dismissable: false,
relativeToBody: true
});
},
function() {
StackExchange.helpers.removeMessages();
}
);
});
});
Nov 19 '18 at 21:26
This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.
The difference is that the questions around this topic don't address specifically selenium on New Relic frame work. The script is running properly with my local dev environment but fails with New Relic. I spent a lot of hours trying to find solutions and work around. @ DebanjanB if you have the solution please let me know.
– Samoht Rusconi
Nov 19 '18 at 21:37
add a comment |
This question already has an answer here:
Selenium Web Driver & Java. Element is not clickable at point (x, y). Other element would receive the click
5 answers
I am having some struggle with my Selenium JS in New relic. I am trying to click an element and I am keeping get back the error "Element is not clickable at point". The solutions at the tread Selenium Web Driver & Java. Element is not clickable at point (x, y). Other element would receive the click are not really applicable to NewRelic.
The snippet I am using is
.then(function() {
log(26, 'clickElement "//form[@id='giftcard-form']/div[3]/div/button"');
return $browser.waitForAndFindElement(By.xpath("//form[@id='giftcard-form']/div[3]/div/button"), DefaultTimeout); })
.then(function (el) { el.click(); })
I don't see anything wrong with the code and the element is visible on the page.
![enter image description here][1]
Any suggestions? it seems a common issue but I didn't have luck with the solutions offered in the other thread
Thanks,
Thomas
javascript selenium selenium-webdriver newrelic
asked Nov 19 '18 at 20:27
Samoht RusconiSamoht Rusconi
104
This question already has an answer here:
Selenium Web Driver & Java. Element is not clickable at point (x, y). Other element would receive the click
5 answers
I am having some struggle with my Selenium JS in New relic. I am trying to click an element and I am keeping get back the error "Element is not clickable at point". The solutions at the tread Selenium Web Driver & Java. Element is not clickable at point (x, y). Other element would receive the click are not really applicable to NewRelic.
The snippet I am using is
.then(function() {
log(26, 'clickElement "//form[@id='giftcard-form']/div[3]/div/button"');
return $browser.waitForAndFindElement(By.xpath("//form[@id='giftcard-form']/div[3]/div/button"), DefaultTimeout); })
.then(function (el) { el.click(); })
I don't see anything wrong with the code and the element is visible on the page.
![enter image description here][1]
Any suggestions? it seems a common issue but I didn't have luck with the solutions offered in the other thread
Thanks,
Thomas
This question already has an answer here:
Selenium Web Driver & Java. Element is not clickable at point (x, y). Other element would receive the click
5 answers
javascript selenium selenium-webdriver newrelic
javascript selenium selenium-webdriver newrelic
asked Nov 19 '18 at 20:27
Samoht RusconiSamoht Rusconi
104
asked Nov 19 '18 at 20:27
Samoht RusconiSamoht Rusconi
104
edited Nov 19 '18 at 22:18
Samoht Rusconi
asked Nov 19 '18 at 20:27
Samoht RusconiSamoht Rusconi
104
asked Nov 19 '18 at 20:27
Samoht RusconiSamoht Rusconi
104
asked Nov 19 '18 at 20:27
Samoht RusconiSamoht Rusconi
104
104
marked as duplicate by DebanjanB selenium
Users with the selenium badge can single-handedly close selenium questions as duplicates and reopen them as needed.
StackExchange.ready(function() {
if (StackExchange.options.isMobile) return;
$('.dupe-hammer-message-hover:not(.hover-bound)').each(function() {
var $hover = $(this).addClass('hover-bound'),
$msg = $hover.siblings('.dupe-hammer-message');
$hover.hover(
function() {
$hover.showInfoMessage('', {
messageElement: $msg.clone().show(),
transient: false,
position: { my: 'bottom left', at: 'top center', offsetTop: -7 },
dismissable: false,
relativeToBody: true
});
},
function() {
StackExchange.helpers.removeMessages();
}
);
});
});
Nov 19 '18 at 21:26
This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.
marked as duplicate by DebanjanB selenium
Users with the selenium badge can single-handedly close selenium questions as duplicates and reopen them as needed.
StackExchange.ready(function() {
if (StackExchange.options.isMobile) return;
$('.dupe-hammer-message-hover:not(.hover-bound)').each(function() {
var $hover = $(this).addClass('hover-bound'),
$msg = $hover.siblings('.dupe-hammer-message');
$hover.hover(
function() {
$hover.showInfoMessage('', {
messageElement: $msg.clone().show(),
transient: false,
position: { my: 'bottom left', at: 'top center', offsetTop: -7 },
dismissable: false,
relativeToBody: true
});
},
function() {
StackExchange.helpers.removeMessages();
}
);
});
});
Nov 19 '18 at 21:26
This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.
The difference is that the questions around this topic don't address specifically selenium on New Relic frame work. The script is running properly with my local dev environment but fails with New Relic. I spent a lot of hours trying to find solutions and work around. @ DebanjanB if you have the solution please let me know.
– Samoht Rusconi
Nov 19 '18 at 21:37
add a comment |
The difference is that the questions around this topic don't address specifically selenium on New Relic frame work. The script is running properly with my local dev environment but fails with New Relic. I spent a lot of hours trying to find solutions and work around. @ DebanjanB if you have the solution please let me know.
– Samoht Rusconi
Nov 19 '18 at 21:37
The difference is that the questions around this topic don't address specifically selenium on New Relic frame work. The script is running properly with my local dev environment but fails with New Relic. I spent a lot of hours trying to find solutions and work around. @ DebanjanB if you have the solution please let me know.
– Samoht Rusconi
Nov 19 '18 at 21:37
The difference is that the questions around this topic don't address specifically selenium on New Relic frame work. The script is running properly with my local dev environment but fails with New Relic. I spent a lot of hours trying to find solutions and work around. @ DebanjanB if you have the solution please let me know.
– Samoht Rusconi
Nov 19 '18 at 21:37
add a comment |
1 Answer
1
active
oldest
votes
waitForAndFindElement will wait only for element present. It will not wait for element visibility.
Try by waiting for the visibility of the element,
.then(function() {
log(26, 'clickElement "//form[@id='giftcard-form']/div[3]/div/button"');
return $browser.wait($driver.until.elementIsVisible($browser.findElement(By.xpath("//form[@id='giftcard-form']/div[3]/div/button"))));
}).then(function (el) {
el.click();
})
If you are getting timeout error, then scroll to view and click.
.then(function() {
log(26, 'clickElement "//form[@id='giftcard-form']/div[3]/div/button"');
return $browser.waitForAndFindElement(By.xpath("//form[@id='giftcard-form']/div[3]/div/button"), DefaultTimeout); })
.then(function (el) {
$browser.executeScript("arguments[0].scrollIntoView()", el);
el.click();
})
If the scroll doesn't help, then at last go with javascript click,
.then(function() {
log(26, 'clickElement "//form[@id='giftcard-form']/div[3]/div/button"');
return $browser.waitForAndFindElement(By.xpath("//form[@id='giftcard-form']/div[3]/div/button"), DefaultTimeout); })
.then(function (el) {
$browser.executeScript("arguments[0].click()", el);
})
answered Nov 19 '18 at 21:04
NavarasuNavarasu
1,8931821
Comments are not for extended discussion; this conversation has been moved to chat.
– Samuel Liew♦
Nov 21 '18 at 2:17
The first snippet did the trick after increasing the timeout to 180000 ms
– Samoht Rusconi
Nov 29 '18 at 17:18
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
waitForAndFindElement will wait only for element present. It will not wait for element visibility.
Try by waiting for the visibility of the element,
.then(function() {
log(26, 'clickElement "//form[@id='giftcard-form']/div[3]/div/button"');
return $browser.wait($driver.until.elementIsVisible($browser.findElement(By.xpath("//form[@id='giftcard-form']/div[3]/div/button"))));
}).then(function (el) {
el.click();
})
If you are getting timeout error, then scroll to view and click.
.then(function() {
log(26, 'clickElement "//form[@id='giftcard-form']/div[3]/div/button"');
return $browser.waitForAndFindElement(By.xpath("//form[@id='giftcard-form']/div[3]/div/button"), DefaultTimeout); })
.then(function (el) {
$browser.executeScript("arguments[0].scrollIntoView()", el);
el.click();
})
If the scroll doesn't help, then at last go with javascript click,
.then(function() {
log(26, 'clickElement "//form[@id='giftcard-form']/div[3]/div/button"');
return $browser.waitForAndFindElement(By.xpath("//form[@id='giftcard-form']/div[3]/div/button"), DefaultTimeout); })
.then(function (el) {
$browser.executeScript("arguments[0].click()", el);
})
answered Nov 19 '18 at 21:04
NavarasuNavarasu
1,8931821
Comments are not for extended discussion; this conversation has been moved to chat.
– Samuel Liew♦
Nov 21 '18 at 2:17
The first snippet did the trick after increasing the timeout to 180000 ms
– Samoht Rusconi
Nov 29 '18 at 17:18
add a comment |
waitForAndFindElement will wait only for element present. It will not wait for element visibility.
Try by waiting for the visibility of the element,
.then(function() {
log(26, 'clickElement "//form[@id='giftcard-form']/div[3]/div/button"');
return $browser.wait($driver.until.elementIsVisible($browser.findElement(By.xpath("//form[@id='giftcard-form']/div[3]/div/button"))));
}).then(function (el) {
el.click();
})
If you are getting timeout error, then scroll to view and click.
.then(function() {
log(26, 'clickElement "//form[@id='giftcard-form']/div[3]/div/button"');
return $browser.waitForAndFindElement(By.xpath("//form[@id='giftcard-form']/div[3]/div/button"), DefaultTimeout); })
.then(function (el) {
$browser.executeScript("arguments[0].scrollIntoView()", el);
el.click();
})
If the scroll doesn't help, then at last go with javascript click,
.then(function() {
log(26, 'clickElement "//form[@id='giftcard-form']/div[3]/div/button"');
return $browser.waitForAndFindElement(By.xpath("//form[@id='giftcard-form']/div[3]/div/button"), DefaultTimeout); })
.then(function (el) {
$browser.executeScript("arguments[0].click()", el);
})
answered Nov 19 '18 at 21:04
NavarasuNavarasu
1,8931821
Comments are not for extended discussion; this conversation has been moved to chat.
– Samuel Liew♦
Nov 21 '18 at 2:17
The first snippet did the trick after increasing the timeout to 180000 ms
– Samoht Rusconi
Nov 29 '18 at 17:18
add a comment |
waitForAndFindElement will wait only for element present. It will not wait for element visibility.
Try by waiting for the visibility of the element,
.then(function() {
log(26, 'clickElement "//form[@id='giftcard-form']/div[3]/div/button"');
return $browser.wait($driver.until.elementIsVisible($browser.findElement(By.xpath("//form[@id='giftcard-form']/div[3]/div/button"))));
}).then(function (el) {
el.click();
})
If you are getting timeout error, then scroll to view and click.
.then(function() {
log(26, 'clickElement "//form[@id='giftcard-form']/div[3]/div/button"');
return $browser.waitForAndFindElement(By.xpath("//form[@id='giftcard-form']/div[3]/div/button"), DefaultTimeout); })
.then(function (el) {
$browser.executeScript("arguments[0].scrollIntoView()", el);
el.click();
})
If the scroll doesn't help, then at last go with javascript click,
.then(function() {
log(26, 'clickElement "//form[@id='giftcard-form']/div[3]/div/button"');
return $browser.waitForAndFindElement(By.xpath("//form[@id='giftcard-form']/div[3]/div/button"), DefaultTimeout); })
.then(function (el) {
$browser.executeScript("arguments[0].click()", el);
})
answered Nov 19 '18 at 21:04
NavarasuNavarasu
1,8931821
waitForAndFindElement will wait only for element present. It will not wait for element visibility.
Try by waiting for the visibility of the element,
.then(function() {
log(26, 'clickElement "//form[@id='giftcard-form']/div[3]/div/button"');
return $browser.wait($driver.until.elementIsVisible($browser.findElement(By.xpath("//form[@id='giftcard-form']/div[3]/div/button"))));
}).then(function (el) {
el.click();
})
If you are getting timeout error, then scroll to view and click.
.then(function() {
log(26, 'clickElement "//form[@id='giftcard-form']/div[3]/div/button"');
return $browser.waitForAndFindElement(By.xpath("//form[@id='giftcard-form']/div[3]/div/button"), DefaultTimeout); })
.then(function (el) {
$browser.executeScript("arguments[0].scrollIntoView()", el);
el.click();
})
If the scroll doesn't help, then at last go with javascript click,
.then(function() {
log(26, 'clickElement "//form[@id='giftcard-form']/div[3]/div/button"');
return $browser.waitForAndFindElement(By.xpath("//form[@id='giftcard-form']/div[3]/div/button"), DefaultTimeout); })
.then(function (el) {
$browser.executeScript("arguments[0].click()", el);
})
answered Nov 19 '18 at 21:04
NavarasuNavarasu
1,8931821
edited Nov 20 '18 at 0:12
answered Nov 19 '18 at 21:04
NavarasuNavarasu
1,8931821
answered Nov 19 '18 at 21:04
NavarasuNavarasu
1,8931821
answered Nov 19 '18 at 21:04
NavarasuNavarasu
1,8931821
1,8931821
Comments are not for extended discussion; this conversation has been moved to chat.
– Samuel Liew♦
Nov 21 '18 at 2:17
The first snippet did the trick after increasing the timeout to 180000 ms
– Samoht Rusconi
Nov 29 '18 at 17:18
add a comment |
Comments are not for extended discussion; this conversation has been moved to chat.
– Samuel Liew♦
Nov 21 '18 at 2:17
The first snippet did the trick after increasing the timeout to 180000 ms
– Samoht Rusconi
Nov 29 '18 at 17:18
Comments are not for extended discussion; this conversation has been moved to chat.
– Samuel Liew♦
Nov 21 '18 at 2:17
Comments are not for extended discussion; this conversation has been moved to chat.
– Samuel Liew♦
Nov 21 '18 at 2:17
The first snippet did the trick after increasing the timeout to 180000 ms
– Samoht Rusconi
Nov 29 '18 at 17:18
The first snippet did the trick after increasing the timeout to 180000 ms
– Samoht Rusconi
Nov 29 '18 at 17:18
add a comment |
The difference is that the questions around this topic don't address specifically selenium on New Relic frame work. The script is running properly with my local dev environment but fails with New Relic. I spent a lot of hours trying to find solutions and work around. @ DebanjanB if you have the solution please let me know.
– Samoht Rusconi
Nov 19 '18 at 21:37