Browser Change

NPAPI and Java plugin support removed from major browsers AI-researched

Dependency: NPAPI / Java browser plugins

Browser vendors removed the NPAPI plugin architecture (Chrome 45 milestone; later Firefox and Safari), stranding Java applets and other plugin-era net artworks unless run in legacy environments.

Affected Artworks

Instance City Total loss Dead

Riccardo Zanardelli

Java Applet embedded in HTML. Applet won't load because browsers no longer run Java plugins.

The Slow Arrow of Beauty Total loss Dead

Victor Liu

Java applet UI + network retrieval. Plugin removal blocks execution.

The Great Game Total loss Dead

John Klima

Java applet realtime 3D terrain visualization. No Java plugin runtime in modern browsers.

art from text Total loss Dead

Roberto Echen

Java applet generating visuals from user text. Applet blocked/unsupported.

StarryNight Total loss Dead

Mark Tribe, Alex Galloway & Martin Wattenberg

Java applet generates constellations. Requires emulation or legacy setup.

Fixes & Mitigations

  • Emulation: Preserve a 'known-good' browser+plugin stack via virtualization (e.g., Windows XP/7 + old Firefox/IE + JRE plugin) with network quarantining.
  • Rebuild: Migrate applet logic to JavaScript/WebGL, or capture an archival recording plus source/code documentation.

NPAPI was progressively disabled and then removed. Chrome’s roadmap explicitly targeted permanent removal by September 2015 (Chrome 45). Firefox later removed NPAPI plugins except Flash (Firefox 52). Safari 12 removed support for most legacy web plugins.

What changed

The NPAPI plugin architecture had allowed browsers to run Java applets, Silverlight, Unity Web Player, and other plugin-based content. Its removal stranded an entire generation of web-based interactive artworks that depended on these runtime environments.

Notes

Scope: any artwork relying on Java, Silverlight, Unity Web Player, etc. Reversibility: medium — VM-based access is feasible, but web-native access typically requires rewrite.

Links