Yup, each version of Chrome has its own special and AFAIK undocumented changes that could impact the connector. The only solution is that someone steps forward to debug and figure out what the latest problems are with the connector and provides patches to Apache NetBeans GitHub. I might take a look but there’s 100 other things I might take a look at too.
Gj On Wednesday, February 13, 2019, Philip Durbin <philipdur...@gmail.com> wrote: > Hi! I've been a fan of the Netbeans Connector Chrome Extension for years > and recommend it in the dev guide for our project. > > Unfortunately, it stopped working for me. The most significant change I've > made lately is upgrading to OS X Mojave (I'm currently on 10.14.2). I'm > using NetBeans 8.2. > > I tried removing the extension from Chrome and re-adding it. > > When I click "Run" on my Java EE 7 project, a new Chrome tab opens with an > address of file:///private/var/folders/c2/qts2_ > 6zn7cl5h8g8x7r7xcbr0000gn/T/blank678733039306727859.html (for example) > and blank page. The content of that HTML page is this: > > <html :netbeans_temporary="true"></html> > > Nothing happens after this blank page shows up. The extension isn't > working. > > Any advice on how I can get this working again? > > Thanks! > > Phil >
