Igal

Almost two years since last comment... Did either of you end up figuring it out? I seem to bump against exactly the same issue

+1 would really like to have this (or similar fix) merged High ROE - small change which makes life easier!

Any updates??

I created #24 please take a look and lmk wdyt 🙏🏼

The problem is, the user has many ways to modify the maps. With the mouse, with touch, with keyboard (affecting pitch, bearing etc). It seems a little overwhelming to try...

IDK. Zooming out on the subject, asking "Is the user responsible for this event?" seems an important enough question to deserve a native answer

I wonder if I can rely on the existence of `event.originalEvent`, where `event` is the first argument to the `moveend` callback. `originalEvent` is missing if the the map view changes...

+1

+1 thank you!

@wilcraig thank you! FYI there's an addition you can make to align this module with common npm-publishing conventions (see packages such as `ngSanitize`, `ngAnimate`, and more): At the module's root...