Angular docset showing white screen

[jshamg]

Hi,

I'am using Zeal version 0.6.1 and every document in the angular (2+) docset is just showing a white page...
Every else docset I downloaded is working properly...

Hope for a fix soon. Greetings!

[iqfy-joe]

I'm also seeing this issue, Zeal 0.6.1 on Ubuntu 18.04; Appears to be isolated to the Angular docset

[jshamg]

@iqfy-joe Is nobody caring about that? 😅 I mean I'm just using Angular, pretty stupid that I'm keeping this tool... Seems like nobody is fixing it...

[ergoproxy623]

Hello! Who knows why Angular 2 does not work?

[richarson]

I don't believe it will help, but: Have you tried reinstalling/updating the docset?

Zeal projects doesn't maintain docsets but uses Dash's, you might want to ping @Kapeli about this issue.

[Kapeli]

No Dash user has reported any issues with the Angular docsets. If anyone is willing to debug and look at what's going wrong, I'm willing to update the docsets to fix it.

One thing to do would be to check if Zeal is using the correct Angular feeds, which are AngularJS.xml (for 1.x) and Angular.xml (for 2.x to 8.x).

[makzan]

It does work when right clicking mouse and open the doc in web browser.

[jshamg]

I have tried reinstalling/updating... still not working...

[jshamg]

@makzan I cant rightclick and open the docset in the browser... How do you do that? :)

[trollixx]

The problem is caused by the webview failing to parse JS (more details in #1127 (comment)). Actual browsers have no such issues, so perhaps this will not get addressed until Qt WebKit gets updated to the newer WebKit, or we switch to Qt WebEngine.

I think the root of the issue might be the CORS not working for file:// URLs, hence polyfills not getting loaded. I see related errors in the real browsers as well, but their JS engines do not require the polyfills to work.

I'll see if I can make a quick change to start serving docset content over HTTP, and whether that solves the issue in the first place.

[jshamg]

@trollixx a quick fix would be fantastical. I'm on vacation right now and taking my laptop everywhere I go... Sometimes I don't have internet, that's why I would really appreciate a quick solution. Thank you very much! :)

[Mutembeijoe]

Same problem here on Manjaro.

[martine777]

Same problem, a quick fix would be appreciated.

[jshamg]

@trollixx no fix soon?

[vpArth]

Looks like Qt webview is using Edge engine, because these pages fail to load in the old Edge(beta chromium edge works fine)

Is there a way to replace engine used without waiting for app update?

[jshamg]

no fix coming?

[trollixx]

Okay, for the time being I disabled JS for the Angular docset. I don't see a better solution, until we either switch to QWebEngine, or Qt WebKit is rebased on top of a more recent upstream version.

[trollixx]

To get the fix please refresh the list of docsets, and then reinstall the docset.

[iHmD]

still giving blank screen even after the refresh and update, am I the only one???

[jshamg]

I test that later (:

[djmbritt]

still giving blank screen even after the refresh and update, am I the only one???

Same here.

[trollixx]

Please verify that meta.json in the docset folder has isJavaScriptEnabled set to false.

[djmbritt]

Can verify.

{
    "extra": {
        "isJavaScriptEnabled": false
    },
    "name": "Angular",
    "revision": "0",
    "title": "Angular",
    "version": "8.2.8"
}

[iHmD]

same content as @djmbritt
"extra": { "isJavaScriptEnabled": false },

[jshamg]

same here... "fix" not working. still showing blank screen.

[GuillaumeSerrat]

Same here. Had an older version that was showing fine till I updated yesterday. Till then blank page.

Tried the fix but didn't work :(

[renaldas-kerpe-arria]

Same here, it was working fine until a few days ago when I updated the docs. I wish I stayed on 7 now 😞.

Any update on the fix?

[trollixx]

Please try one of the CI builds. It looks like v0.6.1 didn't have a fix for per docset JS enablement.

[renaldas-kerpe-arria]

Please try one of the CI builds. It looks like v0.6.1 didn't have a fix for per docset JS enablement.

Thanks, the latest build seems to work fine!

Just FYI: I did notice however that all Angular doc pages now have some seemingly random text at the very bottom of every page, but that seems harmless:

[trollixx]

The text says JS is required for the website to work.

[cuno92]

still giving blank screen on version 0.6.1

[soichirou]

Will there be a fix planned for 0.6.1?

[trollixx]

Both Chromium and Firefox fail to display the HTML pages as well. I think there's something wrong with base path:

ERROR Error: "The selector "aio-shell" did not match any elements"
ERROR Error: "No base href set. Please provide a value for the APP_BASE_HREF token or add a base element to the document."

It doesn't work when served over HTTP (with #1182) either.

I am not sure how Dash shows the docs, but most likely it puts them under a different internal URL.

[GuillaumeSerrat]

If you want to bypass this issue the docset is still valid and accessible via your favorite browser....

Copypasta the following urls in your browser and replace the {drive} and {username} parameters:
-file:///{drive}:/Users/{userName}/AppData/Local/Zeal/Zeal/docsets/Angular.docset/Contents/Resources/Documents/

• file:///{drive}:/Users/{userName}/AppData/Local/Zeal/Zeal/docsets/Angular.docset/Contents/Resources/Documents/material.angular.io.html

[thariqnu-ifm]

If you want to bypass this issue the docset is still valid and accessible via your favorite browser....

Copypasta the following urls in your browser and replace the {drive} and {username} parameters:
-file:///{drive}:/Users/{userName}/AppData/Local/Zeal/Zeal/docsets/Angular.docset/Contents/Resources/Documents/

• file:///{drive}:/Users/{userName}/AppData/Local/Zeal/Zeal/docsets/Angular.docset/Contents/Resources/Documents/material.angular.io.html

I can confirm that this trick is working for me.

Basically, we can browse any of the downloaded docsets using any browser of our choice. To see where the downloaded docsets is being stored on the disk = click Edit > Preferences > General tab > Docset storage section > see the path within Directory. Then you can copy the path to your browser.

[Zeioth]

It seems it's being fixed in the master branch.

[almeno]

A quick solution would be to delete the file that starts with "runtime-es5."
which is located in the folder "Angular.docset \ Contents \ Resources \ Documents \ angular.io"
Example: "runtime-es5.dbabbb81d8abd9e65276"

[vpArth]

No reason to delete files anyway can't be loaded by CORS of file:// restrictions

Why this issue is still closed?
Only way I can read something now is «right click -> Open Desktop Browser»

[mkantonio]

A quick solution would be to delete the file that starts with "runtime-es5."
which is located in the folder "Angular.docset \ Contents \ Resources \ Documents \ angular.io"
Example: "runtime-es5.dbabbb81d8abd9e65276"

this works for me, thanks you so much! :D

[afajansari]

not opening angular docs while deleting 'runtine-es'