Hi,
I observed a strange behaviour when testing webdatamenu under Firefox 14.0.1, sometimes client itemclick won't fire.
After playing a bit with this behaviour it seems that, if the first time you click the item (let`s say Nodo1.1 in the sample), clicking on the item while moving the mouse, as if it were a tiny drag caused by the speed or hurry of the user. After that, item click won't fire. It does not seem to happen on IE. I know that it sounds strange but it is more normal than it seems.
I am using the last service release (12.1.20121.2048).
Any hints?
Sample:
<script> function nodeclick() { alert("click"); } </script>
<ig:WebDataMenu ID="WebDataMenu1" runat="server"> <ClientEvents ItemClick="nodeclick" /> <Items> <ig:DataMenuItem Text="Nodo1"> <Items> <ig:DataMenuItem Text="Nodo1.1"> </ig:DataMenuItem> </Items> </ig:DataMenuItem> </Items> </ig:WebDataMenu>
Thanks.
Hi rickycl,
I was able to reproduce the issue. However, I tested the same sample with the latest internal build and the issue did not occur. So the fix will be available in the next service release, projected for August 24 - http://ko.infragistics.com/help/service-releases/.
If you have any other questions or concerns, please feel free to contact me.
Between steps 2 and 3 move the mouse out of the menu and then hover "Nodo1" and proceed to step 3.
NOTE: it must be the first thing you do on the page, if you click, for example, Nodo1 first then the issue doesn't happen.
I checked ig and ff version and are the same. I am runing the application in debug mode in visual studio 2010's development server on windows 7.
Attached you will find the exact code just in case.
Thanks!
I am still unable to reproduce the issue. This is what I am doing:
Do these steps reproduce the issue on your side? I used NetAdvantage v12.1.2012.1.2048, Firefox 14.0.1.
Using the code from my first post, in Firefox 14.0.1,
1 - Enter the page
2 - Click the inner item, moving the mouse over the item (as if you were a normal user that doesn't now about this issue)
3 - Click the inner item again, this time with the mouse still.
Note: I am "opening" the outer item by hovering but without clicking, if I click on the parent node in order to see the child node it doesn't occur.
Could you provide a sample replicating this behavior as I am so far unable to reproduce it. If I click on an item without moving the mouse, ItemClick is fired.