Using Java Applet option not honored on Mac

If you create a Rich Text field for a web form, and specify Best Fit for OS, it renders the Java applet editor on Safari and Firefox on Windows and Mac as expected, and renders the Dojo editor on Internet Explorer systems. However, when you specify Using Java Applet to force the usage of the Java applet across all systems, the Mac-based Safari and Firefox only render the plain textarea editor (as if HTML was selected as the editor). This seems to be a bug.

Subject: Try this

As a potential workaround, you may also modify the browser.cnf (/data/browser.cnf), and allow the EditorApplet on Mac. Below is a section from the original browser.cnf from 8.5.1FP2 Domino server:

DisableEditorApplet - Boolean indicating whether browser can handle the Editor Applet

Property DisableEditorApplet Boolean False
Rule True MSIE [0-9].; Macintosh # IE on MAC platform
Rule True MSIE [0-9].
; Mac_PowerPC # IE on MAC platform
Rule True ^Mozilla/[0-9].(Macintosh # Netscape on MAC platform
Rule True ^Mozilla/[0-9].
(Mac_PowerPC # Netscape on MAC platform
Rule True Notes # Notes browser

Change the “True” (disable) to “False” (enabled) for ^Mozilla/Mac as follows:

DisableEditorApplet - Boolean indicating whether browser can handle the Editor Applet

Property DisableEditorApplet Boolean False
Rule True MSIE [0-9].; Macintosh # IE on MAC platform
Rule True MSIE [0-9].
; Mac_PowerPC # IE on MAC platform
Rule False ^Mozilla/[0-9].(Macintosh # Netscape on MAC platform
Rule False ^Mozilla/[0-9].
(Mac_PowerPC # Netscape on MAC platform
Rule True Notes # Notes browser

Subject: yes, that works

Thanks, that configuration file allows me to add supported browsers and get the desired behavior. It’s an issue for me that this is only configurable in the file system, since we are in a clustered, enterprise environment where changes like this are greatly discouraged and usually lost over time (e.g the file is overwritten during an upgrade). My hope is that IBM will recognize that these browsers do, in fact, support Java and create a default that reflects that. Alternatively, more control could be given at the application layer to decide what to render.

Again, many thanks for the response. Very helpful.