https://bugs.documentfoundation.org/show_bug.cgi?id=166301
Christian Lohmaier <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW See Also| |https://bugs.documentfounda | |tion.org/show_bug.cgi?id=12 | |5578, | |https://bugs.documentfounda | |tion.org/show_bug.cgi?id=15 | |2172 URL| |https://bugs.launchpad.net/ | |snapd/+bug/1972762 Summary|Installing local help files |Installing local help files |breaks all LO Help on |breaks all LO Help on |Ubuntu (due to Firefox...) |Ubuntu (due to Firefox | |installed as snap package) CC| |[email protected] | |g Ever confirmed|0 |1 --- Comment #1 from Christian Lohmaier <[email protected]> --- Snap packages for browsers are broken by design. Or rather to have the default handler for local files be tied to that browser is. See also https://bugs.launchpad.net/snapd/+bug/1972762 - there are tons of tools that have their documentation stored as HTML files on the local disk and all break because of that. I'm absolutely against creating files in directories not explicitly mentioned for use for temporary files, and especially not outside the LibreOffice profile directory. So creating an additional directory in the users's home for that is not acceptable. "Make the redirector javascript use fetch(url) or XMLHttpRequest to load a tiny test page in the local help tree" If firefox won't load the local page, it won't load javascript/there is nothing to probe for/we cannot tell. And even if it was possible, having a probe file create local files to track info about the users' system is also problematic in itself, or rather something that is something that should be avoided by isolating applications, so that also won't be blessed by me. We force online help when Safari is default browser on macOS since it has similar sandboxing issues https://gerrit.libreoffice.org/c/core/+/73163 and later follow-ups/tweaks So if it is easy to tell whether firefox is a sandboxed version, then using that is the only real way. (but I don't think we're probing actual browser, but just hand the path to xdg-open, so it really should be the system fixing the integration to rewrite that to a URL that firefox can access explaining the problem.) For the user the workaround is to uninstall the local help-packages. -- You are receiving this mail because: You are the assignee for the bug.
