-
Notifications
You must be signed in to change notification settings - Fork 5
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
Blackscreen with qtwebengine (Google and Microsoft login page) #3
Comments
Why does it not merely invoke the default browser, as most software does? |
How would you do that? It would obviously shrink the binary size of the whole app. By most software you probably mean other sign in pages, which don't aim to prevent logins from webbrowsers for third party apps. Yes it is possible if you open the F12 Console and do some hacks, but thats not feasible for the average user. Websecurity make it almost impossible to automate a normal browser session with injected js code Browser extensions have the problem, that every Browser have a different addon system and you need to install it. |
@ChristopherHX, https://auth0.com/docs/authenticate/login/universal-vs-embedded-login#:~:text=With%20Universal%20Login,the%20calling%20app. What I have described is not unusual, yet you appear to believe that it is not solely that, but infeasible. That is usually untrue, especially because services similar to facebook.com have disabled authentication via embedded browsers. |
Current workaround for raspbian.
The mesa drivers for the Raspberry Pi VC4 GPU seems to cause trouble.
This also happen with qtwebengine from offical debian 10 repos, raspbian has no qtwebengine
Defining it within the finish-args would disable gpu acceleration even for x86, x86_64 or arm pc with better drivers which has no such errors.
The text was updated successfully, but these errors were encountered: