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

BiDi follow-ups #20883

Merged
merged 3 commits into from
Aug 13, 2024
Merged

Conversation

martinpitt
Copy link
Member

@martinpitt martinpitt commented Aug 13, 2024

The CDP API would allow calling that when the current context was a
frame. But `WebdriverBidi.locate()` uses the current context and thus
cannot find the iframe there. Set the current context to the toplevel
first to restore the old behaviour.

This fixes cockpit-ostree `OstreeCase.testPermission`.
These skips were due to limitations in the CDP support. With BiDi they
work fine.

Even with BiDi, Firefox still can't handle `eval_js("cockpit.spawn()"`
properly, so keep skipping these tests.

https://issues.redhat.com/browse/COCKPIT-1157
When calling this with `ph_in_text()` or other functions which set a
custom error descriptions, the "condition did not become true" string
match didn't hit, This produced much less useful error output, and also
didn't match existing naughties any more (such as for cockpit-project#4915 in
TestMachinesSettings.testVsock).

Drop the string matching and instead rewrite the exception after the
loop, which is conceptually easier and cleaner anyway.
Copy link
Member

@allisonkarlitskaya allisonkarlitskaya left a comment

Choose a reason for hiding this comment

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

OK.

@allisonkarlitskaya allisonkarlitskaya merged commit 83e1a5a into cockpit-project:main Aug 13, 2024
77 checks passed
@martinpitt martinpitt deleted the bidi-fixes branch August 14, 2024 00:58
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.

2 participants