When running multiple Play apps it's common to assign them different ports using -Dhttp.port. The Chrome plugin only checks port 9000 but instead should "somehow" pick up the configured port(s).

Not sure how to support non-localhost domains without opening everything to the script.

When reloading an Anguar app in the browser, I get the following error a few reloads:

    Error in event handler for 'undefined': Cannot call method 'removeEventListener' of null TypeError: Cannot call method 'removeEventListener' of null
        at bindShortcuts (chrome-extension://alelhddbbhepgpmgidjdcjakblofbmce/javascripts/content_script.js:548:7)
        at chrome-extension://alelhddbbhepgpmgidjdcjakblofbmce/javascripts/content_script.js:78:4
        at Event.dispatchToListener (event_bindings:356:21)
        at Event.dispatch_ (event_bindings:342:27)
        at Event.dispatch (event_bindings:362:17)
        at chromeHidden.Port.dispatchOnConnect.isExternal (miscellaneous_bindings:165:24)
        at Event.dispatchToListener (event_bindings:356:21)
        at Event.dispatch_ (event_bindings:342:27)
        at Event.dispatch (event_bindings:362:17)
        at Object.chromeHidden.Port.dispatchOnMessage (miscellaneous_bindings:253:22) event_bindings:346
    Error in event handler for 'undefined': Cannot read property 'textContent' of null TypeError: Cannot read property 'textContent' of null
        at chrome-extension://dchhggpgbommpcjpogaploblnpldbmen/play-framework-chrome-tools.js:18:32
        at chromeHidden.Port.sendMessageImpl (miscellaneous_bindings:287:9)
        at Event.dispatchToListener (event_bindings:356:21)
        at Event.dispatch_ (event_bindings:342:27)
        at Event.dispatch (event_bindings:362:17)
        at Object.chromeHidden.Port.dispatchOnMessage (miscellaneous_bindings:253:22)
        at chrome-extension://fngmhnnpilhplaeedifhccceomclgfbg/alternet/jquery-1.7.2.min.js:3:25601
        at L (chrome-extension://fngmhnnpilhplaeedifhccceomclgfbg/alternet/jquery-1.7.2.min.js:3:25924)
        at chrome-extension://fngmhnnpilhplaeedifhccceomclgfbg/alternet/jquery-1.7.2.min.js:3:27070
        at chrome-extension://fngmhnnpilhplaeedifhccceomclgfbg/alternet/jquery-1.7.2.min.js:4:29596 

We use Firefox when creating ScalaCourses.com content because Chrome injects weird HTML into web pages modified by the online HTML editor we use. This means we need to run Chrome & Firefox - chrome for displaying error lines for Play apps that don't compile, and Firefox for working with the online HTML editor.

Might it be possible to create a Firefox plugin, similar to the Chrome plugin?

Using Play 2.2.6, IDEA 14.0.1 Ultimate with RemoteCall 1.8, Chromium Version 39.0.2171.65 Ubuntu 14.10 (64-bit), Play Framework Tools Chrome plugin 0.0.12, JDK 1.8.0_25, and XUbuntu 14.10:

WebSocket connection to 'ws://localhost:9001/' failed: Error in connection establishment: 
net::ERR_CONNECTION_REFUSED
chrome-extension://dchhggpgbommpcjpogaploblnpldbmen/play-framework-chrome-tools.js:17 

I wonder if there is some way to link the DOM (via view source & the DOM inspector) and JS source / script inspector to the source in my IDE. I'm not exactly sure yet what the experience would be but putting an issue here to remind me to think more about it. :)

When using Angular's routing, reloads are no longer triggered. I'm assuming it is because of how URLs are constructed, e.g. http://localhost:9000/#/users/1.

I have tested v0.10.0 on Windows, Mac and Linux and it no longer works with Play 2.2.3 apps. I suspect the recent update for Play 2.3.x is the reason. We cannot update Play to 2.3.x so this extension is no longer available to us :(

Is there a way to run an old version of this plugin?

Here: https://github.com/jamesward/play-framework-chrome-tools/settings

Most repos switched already.

Error line clicking doesn't work with Play 2.3 because the error message has changed like this:

In /path/to/file.suffix:6

chrome-extension://dchhggpgbommpcjpogaploblnpldbmen/options.htm

It'd be great if multiple running Play projects could trigger a reload only on their port. #10 didn't make this possible because only one of them will be running the WebSocket, and different projects are running in different JVMs. So maybe this will be solved with sbt 1.0 and its server mode.