December 27, 2025, 5:21am 1
I’ve found that when I change my default app to open text/HTML files from WebPositive to something else such as IceWeasle or Floorp the link to open up the Haiku UserGuide will no longer do so.
It seems to be because the url attribute for the UserGuide points to file:///boot/home/config/settings/WebPositive/LoaderPages/UserGuide, and not to the actual location of the html file for the UserGuide.
I’ve found that the workaround of opening the UserGuide first in WebPositive, dragging and dropping a shortcut to the page to the desktop and using that instead of the UserGuide shortcut will work, even after I change the default browser. Just wondering though what the “LoaderPages” folder actually does in Haiku. Does it somehow enable the UserGuide to be opened…
December 27, 2025, 5:21am 1
I’ve found that when I change my default app to open text/HTML files from WebPositive to something else such as IceWeasle or Floorp the link to open up the Haiku UserGuide will no longer do so.
It seems to be because the url attribute for the UserGuide points to file:///boot/home/config/settings/WebPositive/LoaderPages/UserGuide, and not to the actual location of the html file for the UserGuide.
I’ve found that the workaround of opening the UserGuide first in WebPositive, dragging and dropping a shortcut to the page to the desktop and using that instead of the UserGuide shortcut will work, even after I change the default browser. Just wondering though what the “LoaderPages” folder actually does in Haiku. Does it somehow enable the UserGuide to be opened up in the correct language depending on locale, or something like that? Just wondering.
humdinger December 27, 2025, 8:53am 2
Correct. It’s jvascript that checks if there’s a local version of the userguide, and chooses the online version if there isn’t. It also points to the version of the system’s locale if that exists.
Why other browsers show that error and Web+ doesn’t I don’t know…
XML validators agree that there’s something wrong with line 110: && xmlhttp.responseText.length != 0; but I have no idea what it may be…