$locationChangeSuccess should include info about what triggered it

[coli]

I'd like to distinguish between $locationChangeSuccess triggered by the current page itself (via $location), vs the browser back/forward button.

[coli]

Okay, did some digging, looks like 2 different code paths are triggered.

This is the back/foward path:

    // update $location when $browser url changes
    $browser.onUrlChange(function(newUrl) {
      if ($location.absUrl() != newUrl) {

This is the self update path:

    $rootScope.$watch(function $locationWatch() {
      var oldUrl = $browser.url();
      var currentReplace = $location.$$replace;

      if (!changeCounter || oldUrl != $location.absUrl()) {

So they would just need to fire the same event with a flag added.

[coli]

Looks like the flag should be provided by the caller to $location (and not just a boolean), that way the url change listener can distinguish between the source of the url change and take different actions...

(Our UX is just so complicated...)