HELPALL does not work

[joefiesta]

No description provided.

[gkatsev]

Can you please provide some more information?
I know there's a known issue where the first time you open up :helpall, it shows up blank but if you refresh the page it works. Is this the issue you are seeing?

[joefiesta]

Thanks for responding. I had a problem creating the problem report, so it was rather sparse. But, what else matters?

I am running Firefox 27.0. Vimperator 3.8.2. The page appears with just the word ALL in the upper left. After a REFRESH, that disappears, and the page is blank.

I have tested this after disabling ALL my other extensions and the problem is the same.

Running Windows 7 professional. Any other info that would be helpful, I would be happy to provide.
All other versions of the HELP commands are working fine. It appears to only be HELPALL that is a problem.

[joefiesta]

didn't mean to close issue. How do I indicate I'm done entering info?

[ghost]

I solved my issue with the help page. It was a tab with

liberator://help/options#'urlseparator'

stuck in a collapsed tab tree (a treestyletab bug—sometimes if the firefox was killed and not closed, the old hierarchy vanishes and after restart you have a nice time sorting them back up). Apparently, this tab was not loaded and it caused the help page’s inability to show. Since it got loaded on the first click, no more problems are seen.

[gkatsev]

I think one of the reasons why we're having issues with the help files is because E4X is gone from firefox. This is just a working theory and not actually confirmed yet.

[timss]

I'm getting blank help pages from time to time, but helpall seems to work fine in latest release.

Anyone still facing the issue with helpall and able to reproduce?

[joefiesta]

Just checked back on this issue. It was previously stated that REFRESHING the page after :HELPALL does nothing, takes one to the HELP information. I would like to say that YES, that is still the case. Tried on 3.14.0 and 3.15.0. It was so long that I opened this issue, I had forgotten about the REFRESH workaround.