Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Safely evaluate parents and path for orphan nodes.#81

Open
edlebert wants to merge 2 commits intorubycdp:main from
edlebert:fix-null-parentNode
Open

Safely evaluate parents and path for orphan nodes. #81
edlebert wants to merge 2 commits intorubycdp:main from
edlebert:fix-null-parentNode

Conversation

@edlebert
Copy link

@edlebert edlebert commented Apr 20, 2019

It's possible for Cuprite to evaluate the parents or the path for a node
that no longer belongs to the document.

It's possible for Cuprite to evaluate the parents or the path for a node
that no longer belongs to the document.
Copy link
Member

route commented Apr 22, 2019

@edlebert could you describe scenario when it is possible? Looks like also there'a at least one failing test in all builds

Copy link
Member

route commented Jan 27, 2020

I'll try to rebase and see if it's useful, didn't hear from you ;)

Copy link
Author

Thank you! Yes, it definitely is an issue. It can happen for "waiting" Capybara code such as expect(page).to have_text 'Some Text' when the DOM can change during evaluation.

Copy link
Contributor

Mifrill commented Aug 29, 2021
edited
Loading

okay, we have only one fail test after the merge with the updated master. Not bad! I will take a look, it is also nice to have some tests with the scenario

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

AltStyle によって変換されたページ (->オリジナル) /