What is the vendor support for NPAPI and affected Java applets?

Since early 2016, most browser vendors no longer support the Netscape Plugin Application Programming Interface (NPAPI) architecture. Most Java applet plugins for web browsers rely on NPAPI to render Java applets.

Impact to IBM TRIRIGA applications

The end of NPAPI support prevents the Java applet-based TRIRIGA areas — such as the Gantt, Availability, and Stacking sections — from rendering in IBM TRIRIGA applications on certain browsers.

Areas of TRIRIGA impacted by changes in browser support

The following IBM TRIRIGA areas are impacted. Details on each area follow.

  • Gantt section
  • Availability section
  • Availability Legacy section
  • Stacking section
  • Other Java applet-based TRIRIGA areas…

[Admin: This post is related to the 04.07.16 post about TRIRIGA compatibility with browsers, and the 07.16.15 post about removing NPAPI support from Chrome.]

Continue reading


Where is the latest on IBM TRIRIGA compatibility with browsers?

As of 04.07.16, here are the TRIRIGA “Desktop Client Compatibility” requirements for the following desktop browsers. See the wiki page for the latest requirements.

Third Party Browser Supported Version Notes
Microsoft Internet Explorer 11 See the same note below.
Microsoft Edge 20 See the same note below.
Mozilla Firefox ESR 38.4 See the same note below.
Apple Safari 9.0.1 See the same note below.
Google Chrome 47 See the same note below.
These versions are the minimum versions that are supported for each browser. IBM TRIRIGA will support future versions of a vendor’s browsers if the vendor does not remove, or explicitly or inadvertently disable, functionality that IBM TRIRIGA products rely on. Although future versions are supported, any issue that is introduced as a result of a browser upgrade might require an IBM TRIRIGA Platform fix pack or IBM TRIRIGA Platform upgrade to be fully supported.

Edge and Chrome do not support the NPAPI plugin, which prevents Applets from loading. This prevents the Gantt, Availability, and Stacking sections from rendering in IBM TRIRIGA applications.

[Unlike classic IBM TRIRIGA applications,] Perceptive Applications require the support of modern web specifications to function optimally. Only evergreen browsers (Chrome, Firefox, Edge, and Safari) are supported when using Perceptive Applications or creating custom Views in UX Framework. Internet Explorer 11 [IE11] is not supported.

[Admin: This post is related to the 11.14.14 post about the latest compatibility matrix (updated 12.11.15).]

Continue reading

Removing NPAPI support from Chrome for TRIRIGA 3.4.1 and 3.4.2

With Chrome support going away for NPAPI and therefore breaking Java, are there components/features of the TRIRIGA 3.4.1/3.4.2 client that are dependent on Java running on the client machine. The latest I’ve seen from Oracle is they will not do anything to address this change to Chrome (see https://java.com/en/download/faq/chrome.xml).

I believe Application Builder and Administration Console in 3.4.1 are dependent on Java (which already only work in IE9), but is there anything else outside of these that requires working Java? And if we upgrade to 3.4.2, what components and/or features are dependent on Java? I’m thinking since Adobe SVG Viewer is no longer needed, the Application Builder tools may be OK. I’m less sure about the Admin Console, though something has changed in 3.4.2 to allow it to work with Chrome 42. But I’m really more worried about the end user client and if it will continue to work with Chrome once NPAPI is no longer supported.

NPAPI support removal in Chrome only affects applets for us, and as of 3.4.2, the only applets remaining in TRIRIGA are the Gantt Project Scheduler (Capital Projects), the Availability Scheduler (Reservation Management), and the Stacking tool (Strategic Facilities Planning). These will no longer function in Chrome as of their upcoming September update, but will still function in other supported browsers. You are correct that in 3.4.2, Application Builder tools will not be impacted, as we replaced the expression editor applet, and use native browser SVG rather than Adobe or Batik.

Continue reading