Content rendering error in MDN (HTML, JS, CSS) docsets

[dania-prog]

After updating to zeal 0.6.1, the content could not be displayed in the Tabs. Pasted below is the display error.

kindly assist to resolve. Thanks

[sanruby]

error same as , the javascript docset

[mansur-r]

Same error, using just an initial html docset

[antoni-minkiewicz]

Same error

[falegh]

Zeal 0.6.0, Ubuntu 18.04

Content rendering error after installing updates to these docsets:

• CSS
• HTML
• JavaScript
• SVG

React, Bash and some others working fine

[dania-prog]

The following docsets has the error (content rendering error) after installing updates to the docsets:

• CSS
• HTML
• JS
• Java SE11 (the application closes out)
• Java SE9 (the application closes out)
• Perl
• RubyMotion
• SVG
• WordPress
  The rest are functional. Kindly lets know when it has been resolved.

[trollixx]

Docsets produced from MDN (HTML, CSS, JS, SVG) are broken because of the new JS functionality. It appears to be fixed by the mdn/kuma#5996. Unfortunately, WebKit (and also Firefox) can't load polyfills over the file: scheme. I'm looking into possible solutions.

@dania-prog I cannot reproduce crashes with the Java docsets. Is it possible that you are affected by #868?

Perl and RubyMotion docsets didn't have index page set, should be fixed now. Refresh the docset list, and reinstall the docsets.

The WordPress docset has incorrect dashIndexFilePath in Info.plist, no_index_test/index.html doesn't exist. @Kapeli can you take a look? I think the property is redundant because index.html is present.

[Kapeli]

I sometimes set the dashIndexFilePath to inexistent pages to make Dash not show an index for the docset anymore. In a future version of Dash index pages won't be as important anymore, so some docsets won't have them anymore.

[zjffun]

I find it can fix temporary by remove the
CSS.docset\Contents\Resources\Documents\developer.mozilla.org\static\build\js\react-main.ddbbd86b0685.js.

[prurigro]

Nice fix zjiffun-- here's the same solution turned into a little function you can add to your .bashrc that'll fix all the docs with that problem:

zeal-docs-fix() {
    pushd "$HOME/.local/share/Zeal/Zeal/docsets" >/dev/null || return
    find . -iname 'react-main*.js' -exec rm '{}' \;
    popd >/dev/null || exit
}

[trollixx]

I sometimes set the dashIndexFilePath to inexistent pages to make Dash not show an index for the docset anymore. In a future version of Dash index pages won't be as important anymore, so some docsets won't have them anymore.

@Kapeli what does Dash show in such scenario?

[Kapeli]

The current version of Dash shows a home page that looks like this:

[trollixx]

So Dash simply displays its own home page instead of docset's index page?

[Kapeli]

Yes, but only when there's no docset index page. Otherwise, it shows the index page.

Future version of Dash will have a "Show index page" option which the user will have to press specifically (something like how it works on Dash for iOS). For docsets without an index page, I won't show that option.

[trollixx]

Unfortunately, serving MDN docset from a local HTTP server doesn't help. I think even with the polyfills Qt WebKit is just too old, while for example Firefox began to render properly.

Reported Qt WebKit problem in qtwebkit/qtwebkit#922.

Considering the amount of issues with Qt WebKit, at this point it seems like attempting another migration to Qt WebEngine. There is also a pending PR.

[stompy-chum]

@trollixx: Chrome and Chromium have a command-line flag to enable local file serving, in case that's useful:

chrome.exe --allow-file-access-from-files

I use this to test HTML Imports locally, for example.

[swedishpotato]

Is there any view yet on when this might be fixed? We love Zeal and depend on it for serving docsets in a completely offline teaching environment, but since the last docset updates we've lost HTML, CSS, JS etc docsets. Is there any way of getting the old docsets back in the meantime so that we at least have something we can use?

[madand]

@swedishpotato if you have access to any Unix-like OS with Shell (GNU/Linux, MacOSX, *BSD), see #1155 (comment) for easy fix of the docsets.

If you only have Windows, you can manually clean-up the relevant docsets by deleting the offending JS file from each docset's folder:

• JavaScript.docset\Contents\Resources\Documents\developer.mozilla.org\static\build\js\react-main.e49be9481ede.js
• CSS.docset\Contents\Resources\Documents\developer.mozilla.org\static\build\js\react-main.e49be9481ede.js
• HTML.docset\Contents\Resources\Documents\developer.mozilla.org\static\build\js\react-main.e49be9481ede.js

The exact JS filename may differ in that e49be9481ede bit, just look for react-main.<something>.js and delete it.

[jimmylab]

@swedishpotato if you have access to any Unix-like OS with Shell (GNU/Linux, MacOSX, *BSD), see #1155 (comment) for easy fix of the docsets.

If you only have Windows, you can manually clean-up the relevant docsets by deleting the offending JS file from each docset's folder:

• JavaScript.docset\Contents\Resources\Documents\developer.mozilla.org\static\build\js\react-main.e49be9481ede.js
• CSS.docset\Contents\Resources\Documents\developer.mozilla.org\static\build\js\react-main.e49be9481ede.js
• HTML.docset\Contents\Resources\Documents\developer.mozilla.org\static\build\js\react-main.e49be9481ede.js

The exact JS filename may differ in that e49be9481ede bit, just look for react-main.<something>.js and delete it.

Much thanks for your tips!

Here is my batch version:

:: set you own doc path
set DOCPATH=C:\ZealDocs

set CORRUPT_FILE=Contents\Resources\Documents\developer.mozilla.org\static\build\js\react-main.*.js
ren "%DOCPATH%\JavaScript.docset\%CORRUPT_FILE%" *.js.bak
ren "%DOCPATH%\CSS.docset\%CORRUPT_FILE%" *.js.bak
ren "%DOCPATH%\HTML.docset\%CORRUPT_FILE%" *.js.bak
ren "%DOCPATH%\SVG.docset\%CORRUPT_FILE%" *.js.bak
pause

[tonnysi]

Only add slash before %CORRUPT_FILE%

set DOCPATH=C:\ZealDocs
 
set CORRUPT_FILE=Contents\Resources\Documents\developer.mozilla.org\static\build\js\react-main.*.js
ren "%DOCPATH%\JavaScript.docset\%CORRUPT_FILE%" *.js.bak
ren "%DOCPATH%\CSS.docset\%CORRUPT_FILE%" *.js.bak
ren "%DOCPATH%\HTML.docset\%CORRUPT_FILE%" *.js.bak
ren "%DOCPATH%\SVG.docset\%CORRUPT_FILE%" *.js.bak
pause

[anibalsanchez]

A small tweak:

find ~/.local/share/Zeal/Zeal/docsets -name "react-main.*.js" -exec rm --interactive {} \;

[kohane27]

@anibalsanchez Building on top:

If you're on Windows, has Git for Windows, using the default docset storage directory (C:\Users\UserName\AppData\Local\Zeal\Zeal\docsets), then run this script:

find ~/AppData/Local/Zeal/Zeal/docsets -name "react-main.*.js" -exec rm --interactive {} \;

Press Enter a few times to confirm the deletions.

[dblandin]

It took a bit of hunting to find where docsets are installed for a Flatpak-installed setup :

~/.var/app/org.zealdocs.Zeal/data/Zeal/Zeal/docsets

Here's an invocation building off of other comments to clean out these problematic JavaScript files within the docsets:

$ find .var/app/org.zealdocs.Zeal/data/Zeal/Zeal/docsets -name "react-main.*.js" -exec rm {} \;

source: https://docs.flatpak.org/en/latest/sandbox-permissions.html

[J3RN]

Now that this issue is resolved, would it be possible to cut a new release? I'm assuming the package maintainers for the assorted Linux distros (and Flatpak) are watching for a new tagged version to be released before packaging and distributing it.

[2bit-hack]

#1155 (comment) fixed the rendering issue and displays the front page for the JavaScript docset, but whenever I click on any of the other links, I get a QtNetworkError 203.

The exact error is as follows:
Error opening /home/sierrakilo/.local/share/Zeal/Zeal/docsets/JavaScript.docset/Contents/Resources/Documents/developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/eval.html: No such file or directory

This is because the path that was created on my device was .../Global_objects/... instead of .../Global_Objects/.... I fixed it by manually changing the directory name, but it would be nice if this was changed automatically.

I'm using Manjaro Linux KDE, and installed Zeal using pacman. Also, I can confirm this happened only for the JavaScript docset and not the HTML and CSS docsets.

[Zaggar]

If you are using Windows, i think this is more straight forward.

https://www.programmersought.com/article/89484147811/

[lesar]

same problem running on Ubuntu 20.04 64bit desktop on rpi4

way the issue is closed if the problem persist?

[Zaggar]

Then you will have to do same (delete the react-mainxxxxxx.js files) for both HTML.docset and JavaScript.docset

[sgrubsmyon]

same problem running on Ubuntu 20.04 64bit desktop on rpi4

way the issue is closed if the problem persist?

Because, as @trollixx commented on May 5, the issue has been fixed by the port to Qt WebEngine. It just has not been released yet and will enter release v0.7.0. Until that is out, you need to either compile Zeal yourself, try the CI builds or apply the workaround.

[akx]

On Windows, you can use del /s (making it recursive), e.g.

C:\Users\yourusername\AppData\Local\Zeal\Zeal\docsets>del /s/q react-main*js

to find and eradicate the react-main.js files.

[ulag-byte]

have the same problem with zeal 0.6.1, I cant see javascript, html, css

[marui888]

I find it can fix temporary by remove the
CSS.docset\Contents\Resources\Documents\developer.mozilla.org\static\build\js\react-main.ddbbd86b0685.js.
It works, really

[thefonso]

This is broken again. Javascript, css, html docset from mdn are all dark. all other docsets display fine.