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

Opening two tabs with google.com result in "Unknown error while getting elements" #8197

Open
Hi-Angel opened this issue May 13, 2024 · 2 comments

Comments

@Hi-Angel
Copy link
Contributor

Version info:

qutebrowser v3.1.0
Git commit:
Backend: QtWebEngine 6.7, based on Chromium 118.0.5993.220 (from api)
Qt: 6.7.0

And it's also tested with latest main branch.

Does the bug happen if you start with --temp-basedir?:

Yes

Description

See steps to reproduce.

I think it's a regression because I haven't see it before. Idk what component regressed though.

I think this is different from #7662, for one because that issue seems to have been related to a WebEngine bug that was fixed.

How to reproduce

  1. Launch qutebrowser --temp-basedir google.com google.com

    Qutebrowser with two tabs should get opened

  2. Type into the search box test and press Enter

  3. Press f to make hints appear over the results page.

Expected

Hints should appear

Actual

Qutebrowser prints Unknown error while getting elements

@Hi-Angel Hi-Angel changed the title After secondary start, hints on google.com result in "Unknown error while getting elements" Opening two tabs with google.com result in "Unknown error while getting elements" May 13, 2024
@Hi-Angel
Copy link
Contributor Author

Fixed the title (while writing this issue I found a better way to reproduce).

FWIW, "steps to reproduce" isn't the only way to get this. I don't have a habit of having multiple google pages among opened tabs, but I still routinely get the error. It usually happens when I repeat search within the same tab. For some reason though, with --temp-base-dir it does not happen, but it still can be reproduced with the steps I wrote in the post.

@The-Compiler
Copy link
Member

Reproduced, fails with Uncaught TypeError: Cannot read properties of undefined (reading 'webelem').

Seems to work fine with Qt 6.6, so this might be another QtWebEngine 6.7 regression...

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

No branches or pull requests

2 participants