fix dom parsing issue

[LawyZheng]

Important

Fix DOM parsing issue by adding iterable checks for element.attributes in hasNgAttribute() and buildElementObject() in domUtils.js.

• Behavior:
  • Add check for iterable element.attributes in hasNgAttribute() and buildElementObject() in domUtils.js.
  • Log a warning if element.attributes is not iterable in buildElementObject().
• Functions:
  • hasNgAttribute(): Returns false if element.attributes is not iterable.
  • buildElementObject(): Skips attribute processing and logs a warning if element.attributes is not iterable.

^{This description was created by for 3434a52. It will automatically update as commits are pushed.}

[ellipsis-dev]

👍 Looks good to me! Reviewed everything up to 3434a52 in 15 seconds

More details

• Looked at 68 lines of code in 1 files
• Skipped 0 files when reviewing.
• Skipped posting 1 drafted comments based on config settings.

1. skyvern/webeye/scraper/domUtils.js:1089

• Draft comment:
  Consider providing more context in the warning message to help with debugging.

console.warn(`element.attributes is not iterable for element with tagName=${element.tagName} and element_id=${element_id}`);

• Reason this comment was not posted:
  Confidence changes required: 50%
  The PR adds a check for iterable attributes in hasNgAttribute and buildElementObject functions. This is a good practice to prevent errors when element.attributes is not iterable. However, the warning message in buildElementObject could be improved for clarity.

Workflow ID: wflow_ETXHnW5py4TyhBhh

---

You can customize Ellipsis with 👍 / 👎 feedback, review rules, user-specific overrides, quiet mode, and more.