If Collabora can not support Java functionality, whatever the reason, the UI should not include any components that lead the user to believe that they might be able to activate it in some way.
Example : the Preferences dialog, under Advanced, kind of implies that it should be possible to select a JDK and use it for some of the Java functionality that standard TDF LO allows.
This problem isn't Arm-specific and also exists on Intel based Macs.
Steps to Reproduce:
UI contains components that hint at Java support, whereas such support is excluded by choice in the Collabora and LO Vanilla releases
The UI shouldn't contain components for unavailable functionality
User Profile Reset: No
Version : 6.4-17
Build ID : 6f0073b528f4b70b1f0c34714a289ca5cf9f61fc
Threads CPU : 8; OS : Mac OS X 10.16; UI Render : par défaut; VCL: osx;
Locale : fr-FR (fr_FR.UTF-8); Langue IHM : fr-FR
Not sure why this was changed to LOOL instead of LibreOffice.
(In reply to Alex Thurgood from comment #1)
> Not sure why this was changed to LOOL instead of LibreOffice.
I was told on QA IRC to report any bugs in Collabora Office against the LibreOffice product (and/or specific modules).
Note that the --without-java option has been available forever, and is in no way Collabora-specific.
I guess this is an enhancement
This problem is also apparent in LibreOffice Community.
Christian/Stephan: since it concerns specifically macOS, thought you might be interested here.
I'll increase the importance here since people pay for Apple store/Collabora:
- from Apple store 8,99$ according to https://apps.apple.com/us/app/libreoffice/id1630474372
- from Collabora when using for Business and not just test/home use from 22,29$ according to https://www.collaboraoffice.com/subscriptions/
In terms of marketing, I'm afraid it may have more impact (here negative) than to know if we had to use LO 8 or LO 7.6.