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

A couple of common docsets result in Content rendering error #1235

Closed
frispete opened this issue May 25, 2020 · 4 comments
Closed

A couple of common docsets result in Content rendering error #1235

frispete opened this issue May 25, 2020 · 4 comments

Comments

@frispete
Copy link

Hi,

attempting to display some docsets (e.g. CSS, HTML) result in:

image

image

This might be related to a pretty current system (openSUSE Tumbleweed rolling release 20200520), that uses up to date versions of everything (Qt 5.14.1, WebKit 5.212, ...).

Zeal and libs are generated with gcc 9.2.1 (full build log.

It smells like some WebKit issue, but no further console output is triggered from the error.

Any idea, where to dig next?

@data-man
Copy link
Contributor

@frispete

WebKit

Why?

Any idea, where to dig next?

Now Zeal uses Qt WebEngine. See #1125.

@frispete
Copy link
Author

Why?

Probably, because QWebEngine didn't make it to a release.

FWIW, I packaged current git here, and it looks much better now.

I had to reinstall a couple of docsets, and found, that NET Framework is dysfunctional, but who cares about NET... Me was just curious.

Thank you. Very cool piece of software, BTW!

Will promote this version to openSUSE Factory now.

@trollixx
Copy link
Member

@frispete FYI there are still a few unresolved regressions introduced by porting to Qt WebEngine, that's the main reason v0.7.0 is not out yet.

Duplicate of #1155.

@frispete
Copy link
Author

Thanks for the update @trollixx. For my humble usage patterns, current git is in a much better shape than 0.6.1.

Regarding the rendering bugs in #1155, I've yet to come across one of them. 👍

@github-actions github-actions bot locked and limited conversation to collaborators Aug 6, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Development

No branches or pull requests

3 participants