Catching waitForSelector Errors
up vote
0
down vote
favorite
I use a module called Puppeteer.
I tried waiting for a selector on my page that may not appear. Out of the two approaches I took, only the try-catch method worked.
try-catch block - working
try
await page.waitForSelector('.element');
//element appeared
catch (error)
//element did not appear
promise chaining - not working
await page.waitForSelector('.element')
.catch((error) =>
//element did not appear
)
.then(() =>
//element appeared
);
It seems that waitForSelector does return a Promise as indicated in the API, but I can't figure why the latter approach didn't work. It threw the error anyway.
Have anyone encountered the same issue?
javascript node.js automation ui-automation puppeteer
add a comment |
up vote
0
down vote
favorite
I use a module called Puppeteer.
I tried waiting for a selector on my page that may not appear. Out of the two approaches I took, only the try-catch method worked.
try-catch block - working
try
await page.waitForSelector('.element');
//element appeared
catch (error)
//element did not appear
promise chaining - not working
await page.waitForSelector('.element')
.catch((error) =>
//element did not appear
)
.then(() =>
//element appeared
);
It seems that waitForSelector does return a Promise as indicated in the API, but I can't figure why the latter approach didn't work. It threw the error anyway.
Have anyone encountered the same issue?
javascript node.js automation ui-automation puppeteer
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I use a module called Puppeteer.
I tried waiting for a selector on my page that may not appear. Out of the two approaches I took, only the try-catch method worked.
try-catch block - working
try
await page.waitForSelector('.element');
//element appeared
catch (error)
//element did not appear
promise chaining - not working
await page.waitForSelector('.element')
.catch((error) =>
//element did not appear
)
.then(() =>
//element appeared
);
It seems that waitForSelector does return a Promise as indicated in the API, but I can't figure why the latter approach didn't work. It threw the error anyway.
Have anyone encountered the same issue?
javascript node.js automation ui-automation puppeteer
I use a module called Puppeteer.
I tried waiting for a selector on my page that may not appear. Out of the two approaches I took, only the try-catch method worked.
try-catch block - working
try
await page.waitForSelector('.element');
//element appeared
catch (error)
//element did not appear
promise chaining - not working
await page.waitForSelector('.element')
.catch((error) =>
//element did not appear
)
.then(() =>
//element appeared
);
It seems that waitForSelector does return a Promise as indicated in the API, but I can't figure why the latter approach didn't work. It threw the error anyway.
Have anyone encountered the same issue?
javascript node.js automation ui-automation puppeteer
javascript node.js automation ui-automation puppeteer
edited Nov 10 at 6:19
Grant Miller
4,969132648
4,969132648
asked Nov 10 at 2:41
toffee.beanns
199111
199111
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
1
down vote
accepted
You should restructure your Promise Chaining example to use the then() method before the catch() method.
Consider the following example using page.waitForSelector():
// Correct Method
await page.waitForSelector('#example').then(() =>
console.log('SUCCESS');
).catch(e =>
console.log('FAIL');
);
If the element does not exist, then FAIL will be logged to the console. Otherwise, if the element does exist, the output will be SUCCESS.
On the other hand, take a look at the example below in which then() and catch() are reversed:
// Incorrect Method
await page.waitForSelector('#example').catch(e =>
console.log('FAIL');
).then(() =>
console.log('SUCCESS - not necessarily');
);
If the element does not exist, then FAIL will be logged to the console, but regardless of whether the element exists or not, SUCCESS will also be written to the console. This is because logging SUCCESS is the next immediate step in the chain after attempting to catch an error.
Using then() before catch() will allow you to print one of two messages and achieve your desired result.
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
accepted
You should restructure your Promise Chaining example to use the then() method before the catch() method.
Consider the following example using page.waitForSelector():
// Correct Method
await page.waitForSelector('#example').then(() =>
console.log('SUCCESS');
).catch(e =>
console.log('FAIL');
);
If the element does not exist, then FAIL will be logged to the console. Otherwise, if the element does exist, the output will be SUCCESS.
On the other hand, take a look at the example below in which then() and catch() are reversed:
// Incorrect Method
await page.waitForSelector('#example').catch(e =>
console.log('FAIL');
).then(() =>
console.log('SUCCESS - not necessarily');
);
If the element does not exist, then FAIL will be logged to the console, but regardless of whether the element exists or not, SUCCESS will also be written to the console. This is because logging SUCCESS is the next immediate step in the chain after attempting to catch an error.
Using then() before catch() will allow you to print one of two messages and achieve your desired result.
add a comment |
up vote
1
down vote
accepted
You should restructure your Promise Chaining example to use the then() method before the catch() method.
Consider the following example using page.waitForSelector():
// Correct Method
await page.waitForSelector('#example').then(() =>
console.log('SUCCESS');
).catch(e =>
console.log('FAIL');
);
If the element does not exist, then FAIL will be logged to the console. Otherwise, if the element does exist, the output will be SUCCESS.
On the other hand, take a look at the example below in which then() and catch() are reversed:
// Incorrect Method
await page.waitForSelector('#example').catch(e =>
console.log('FAIL');
).then(() =>
console.log('SUCCESS - not necessarily');
);
If the element does not exist, then FAIL will be logged to the console, but regardless of whether the element exists or not, SUCCESS will also be written to the console. This is because logging SUCCESS is the next immediate step in the chain after attempting to catch an error.
Using then() before catch() will allow you to print one of two messages and achieve your desired result.
add a comment |
up vote
1
down vote
accepted
up vote
1
down vote
accepted
You should restructure your Promise Chaining example to use the then() method before the catch() method.
Consider the following example using page.waitForSelector():
// Correct Method
await page.waitForSelector('#example').then(() =>
console.log('SUCCESS');
).catch(e =>
console.log('FAIL');
);
If the element does not exist, then FAIL will be logged to the console. Otherwise, if the element does exist, the output will be SUCCESS.
On the other hand, take a look at the example below in which then() and catch() are reversed:
// Incorrect Method
await page.waitForSelector('#example').catch(e =>
console.log('FAIL');
).then(() =>
console.log('SUCCESS - not necessarily');
);
If the element does not exist, then FAIL will be logged to the console, but regardless of whether the element exists or not, SUCCESS will also be written to the console. This is because logging SUCCESS is the next immediate step in the chain after attempting to catch an error.
Using then() before catch() will allow you to print one of two messages and achieve your desired result.
You should restructure your Promise Chaining example to use the then() method before the catch() method.
Consider the following example using page.waitForSelector():
// Correct Method
await page.waitForSelector('#example').then(() =>
console.log('SUCCESS');
).catch(e =>
console.log('FAIL');
);
If the element does not exist, then FAIL will be logged to the console. Otherwise, if the element does exist, the output will be SUCCESS.
On the other hand, take a look at the example below in which then() and catch() are reversed:
// Incorrect Method
await page.waitForSelector('#example').catch(e =>
console.log('FAIL');
).then(() =>
console.log('SUCCESS - not necessarily');
);
If the element does not exist, then FAIL will be logged to the console, but regardless of whether the element exists or not, SUCCESS will also be written to the console. This is because logging SUCCESS is the next immediate step in the chain after attempting to catch an error.
Using then() before catch() will allow you to print one of two messages and achieve your desired result.
answered Nov 10 at 6:17
Grant Miller
4,969132648
4,969132648
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53235577%2fcatching-waitforselector-errors%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown