Skip to content
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

mark disabled element as interactable #1175

Merged
merged 1 commit into from
Nov 12, 2024

Conversation

LawyZheng
Copy link
Collaborator

@LawyZheng LawyZheng commented Nov 12, 2024

Important

Modify isInteractable in domUtils.js to consider disabled elements interactable if not hidden.

  • Behavior:
    • Modify isInteractable function in domUtils.js to consider elements interactable even if they are disabled, as long as they are not hidden.
  • Functions:
    • Change condition in isInteractable to use isHidden() instead of isHiddenOrDisabled().

This description was created by Ellipsis for 10a5fd2. It will automatically update as commits are pushed.

Copy link
Contributor

@ellipsis-dev ellipsis-dev bot left a comment

Choose a reason for hiding this comment

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

👍 Looks good to me! Reviewed everything up to 10a5fd2 in 28 seconds

More details
  • Looked at 13 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:399
  • Draft comment:
    Consider checking for both hidden and disabled elements to ensure non-interactable elements are correctly identified.
  if (isHiddenOrDisabled(element)) {
  • Reason this comment was not posted:
    Decided after close inspection that this draft comment was likely wrong and/or not actionable:
    The comment is suggesting a change that was explicitly altered in the diff. The author changed the condition from checking both hidden and disabled to only hidden, which might be intentional. The comment does not provide strong evidence that the change is incorrect or that the original condition should be restored.
    I might be missing the context of why the change was made, but the comment does not provide any evidence or reasoning to support reverting the change.
    Without evidence or reasoning, the comment does not meet the criteria for a necessary code change. The author might have a valid reason for the change.
    Delete the comment as it does not provide strong evidence or reasoning to revert the change made in the diff.

Workflow ID: wflow_9VFwNqNP21RloDTc


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

@LawyZheng LawyZheng merged commit 79bc51b into main Nov 12, 2024
2 checks passed
@LawyZheng LawyZheng deleted the lawy/mark-disabled-element-as-interactable branch November 12, 2024 07:35
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.

1 participant