I am using ng-click for div which will filter the data. I am using collection-repeat to show large data.
When the data is less, the click only triggers once, but when the data is huge, the click triggers twice. I tried using fastclick.js but didn't work out. I have only added angularjs once through ionic.bundle.min.js.
I can't put the demo as this is confidential project.
And also, THIS PROBLEM ONLY OCCURS IN IOS, NOT IN ANDROID AND PC
Yes there is problem, sometimes ng-click fires twice.
please check: https://github.com/driftyco/ionic/issues/1022
they have suggested multiple solutions
Related
I am currently using TanStack React Query to make an UI and I have an issue when I invoke queryClient.removeQueries(queryKey) clicking on a button.
The issue is that every click I do, the display flickers once. The cache is correctly cleaned but the flicker is annoying.
Is this a normal behaviour? I would like to solve it.
Thanks in advance!
We are using angular-material's md-tabs to display information to the user.
Up until now we used an on-demand approach by adding
ng-click=vm.getForExampleDataForTab1(),
ng-click=vm.getForExampleDataForTab2()
and so on for each md-tab. But this solution has a problem that the first tab is displayed with no data because it doesn't get clicked by the user. So we switched to md-on-select instead. And that did the trick, the first tab was getting data and all was fine. Apparently. We then discovered in Chrome's Dev tools that when moving to another page in the app, all the other tabs that were not selected (the user didn't click on them to view the data) were called.
Did anyone encounter such a behaviour? It only happens when we used md-on-select, not ng-click on the tabs.
Thanks a lot,
ashilon
I have a situation where an ng-click on a table row with ng-repeat inside a modal window. The click event has always fired in Chrome. Only once every so often, the click event does not fire in Internet Explorer 11.
Is this a known issue with any workaround?
Correction: the click event is firing, and the ajax call behind it is firing, but the results of the ajax call are IE's cached results rather than the results of the latest query.
I believe the problem is described in this question:
Better Way to Prevent IE Cache in AngularJS?
I have this weird issue with my angular app. It doesn't happen every time but I've been able to consistently reproduce it if I click to it as quickly as I can as soon as my angularjs app loads.
Basically my right pane directive will sometimes render a blank page. This page however appears when I resize the browser window a little bit.
I'm not even sure where to begin looking to resolve this bug. I tried messing around with $timeout and $scope.$apply but it didn't seem to do anything.
Has anyone seen anything like this before and if so, how did you resolve it?
Note the directive I use does use ng-include with a value that is dynamically generated from the custom directive's associated controller.
P.S. Another oddity, if I move my mouse over the allow main dock then it loads the page too. (I assume it's doing an unfocus action on the browser window.) I wanted to see if this was a browser specific issue because of this. Looks like it's only Chrome where this is a problem, as I can't reproduce the problem on firefox.
Same problem caused by CSS - display: table, found a solution by changing it to display: inline-block, so check if you have a such.
I created a long form using Angular Material. Weird thing is that instead of the page displaying normally it starts off midway through the form.
Is this something my browser is doing (Perhaps it thinks I left off at a certain point last time)?
Not sure how to force the page to load normally and start from the top.
Has anyone encountered this before?
I was able to track down the issue and it was the md-autocomplete field causing the page to scroll down. To fix this I added md-autofocus="false" in the md-autocomplete field and now it loads normally.