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

otter-browser open about:blank#blocked page instead "home screen" #1596

Closed
AngryPenguinPL opened this issue Oct 17, 2019 · 4 comments
Closed

Comments

@AngryPenguinPL
Copy link

@AngryPenguinPL AngryPenguinPL commented Oct 17, 2019

We recently discovered that Otter-browser after opening instead of showing the so-called "home screen", opens an empty tab - about:blank#blocked.

If we take a good look, the "home screen" appears after the start literally for half a second, and then about:blank#blocked appears. The same behavior appears when you open a new tab.
Just like in gif below:

Peek 2019-10-10 16-06

(here is a backup if above gif dont load https://imgur.com/eUVxbZu)

Is there any logical explanation or is it a bug, maybe a packing issue? Can we fix it somehow?
Here is ours spec: https://github.com/OpenMandrivaAssociation/otter-browser

@aurhat
Copy link
Contributor

@aurhat aurhat commented Oct 18, 2019

Could you check in the current master branch? 36478f2 - this commit should fix the problem (likely).

@AngryPenguinPL
Copy link
Author

@AngryPenguinPL AngryPenguinPL commented Oct 19, 2019

Yes, in version build from master branch this issue is fixed. So I thnk I can create patch from this commit to current stable.

Thanks.

@Emdek
Copy link
Member

@Emdek Emdek commented Oct 20, 2019

@AngryPenguinPL, I've added it to the list of commits to backport, I'm planning to push 1.0.02 soonish.

@Emdek
Copy link
Member

@Emdek Emdek commented Oct 20, 2019

It was broken by QtWebEngine update, I don;t remember which one was it exactly, perhaps 5.12 or 5.13.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants