core: Handle DOM.resolveNode errors

[webcarrot]

Summary
Catch DOM.resolveNode errors.

Related Issues/PRs
Issue: #2736

[googlebot]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here (e.g. I signed it!) and we'll verify it.

---

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

[googlebot]

CLAs look good, thanks!

[webcarrot]

@paulirish
It works for me but I'm not sure if it should not be handled elsewhere - I do not know this project and flows in it.

[patrickhulce]

thanks @webcarrot this is a great start!

[brendankenny]

FWIW I'm not sure we should fail silently here because the semantics end up being a bit weird (pretending the property doesn't exist when it's actually the element that doesn't). It seems like the caller should handle the exception (like it now does above in all-event-listeners).

[patrickhulce]

This is consistent with the current behavior of the method though, returning null when the object does not exist. If we keep throwing here, we should convert the above to throw and change the typedef

[brendankenny]

Ah, good point, I missed the first check. I wonder if we ever actually fail here then. The issue seems like it's been the event listener gatherer that's been failing. All good regardless.