ng-click no longer working at all across my mobile app

[jeffthompson1971]

Just moved to the latest-greatest material, and now my whole app is broken. ng-click is never fired for any of my controls on any of my webviews. FYI I'm building an appgyver supersonic app. I've been using ng-click with angular-material for the past 6 months with no issues at all. But now it's broken with 100% consistency.

Is this a know issue? should I be using some other events other than ng-click in my angular app?

[gustavohenke]

I've been using v0.8.0-rc1 for a week, and have no issues.
You should probably post a plunkr/codepen/<insert snippet site here> so guys can help you debug the problem.

[jeffthompson1971]

my app is a bit to large/complicated to try to put a code-pen together.. needs to be run in a simulator or real device. not sure of any way to share it easily.

So you are also using appgyver/supersonic with angular-material for the UI? If so are you just using ng-click ?

I just did do this though.. i'm in the process of building a web-page that re-uses most of my angular services etc. that I use on my mobile app. And I also just pulled in latest/greatest angular-material. basically i just started with the angular-material-seed app. that app has a button that opens the left drawer. It works fine on my desktop browser, but from my android device in chrome, the touch fails. pressing that button does nothing. I"m assuming this is the same issue?

if you have a mobile device, can you try to open this link in your browser and see if pressing the button in the upper right corner works?

---

I see this issue also:
#1403

if you read it seems maybe general touch issue as well perhaps? hmmmm the plot thickens ... :)

[gustavohenke]

Hmmm, I spoke too soon.
In my own app, I activated the touch emulation in Chrome DevTools and found that some clicks are never fired.

The following issues may be related to this one: #1406, #1528

And no, I don't use Appgyver, I'm using plain Cordova,

[gustavohenke]

In my case, I just found that I depended upon ngTouch module, which conflicted with ngMaterial.
For now, my clicks are working back again.

[jeffthompson1971]

are you saying I need to use ngTouch? I just verified that going back to the older version of material works fine so clearly this is new breakage across the board. I was reading about their removing hammer so guessing that's the breakage.

when can we expect a fix? is ngTouch a work-around or a proper dependency?

UPDATE - I tried to pull in ng-touch, but still not getting any events, at least via ng-click.

[marcysutton]

$mdGestures is still causing problems. This is indeed a related issue: #1406

[gustavohenke]

are you saying I need to use ngTouch?

No, with ngTouch I had problems. Without it = all green.

[jeffthompson1971]

Not for me. Is there a fix on the way?

Also gustavo - what is your tech stack? are you saying this is working for you on a mobile device or just web browser? for me... if i pull in ngTouch then I can get the swipe working fine, but click never fires so it's useless.

[jeffthompson1971]

I really need to know if the angular-material team recognizes the breakage from 7 to 8 is indeed there and if there is a fix planned. If the answer is 'go away we don't care about your issue' that's valid, I'd just like to know so I can move onto another UI solution.

I just did a final test to make it quite clear there is breakage on ng-click...

Starting from my broken build that pulls in the latest v8 angular-material what i did was:

1. git checkout 69462fe // commit id for one of the v7 builds
2. gulp build
3. reload my app

and everything is perfect again. i know that hammer was pulled out etc. so clearly there was code churn around touch events right? clearly there is an issue and my question is if it will be addressed or not. I can move on I just need to know what the plan is. appreciate a quick comment letting me know the status...

[ThomasBurleson]

@jeffthompson1971 - we definitely care about this issue. Improving $mdGestures is a priority for us. Please expect some fixes/traction on this in the near future.