Errm, could you provide more Informations please. Here a Guide to do it the proper Way (expecially a reduced Testcase/URL showing the Issue): https://developer.mozilla.org/en/Bug_writing_guidelines
A radgrid contains a bound item, that has a linkbutton. When clicking the linkbutton, it will call the itemcommand event. This is fired. In the itemcommand event if you have a response.redirect ( some page) it will error out. The grid is ajaxified, along with a radajaxpanel around the grid. This is a bad bug, and i see more people have this same issue... Everything worked in firefox 3, not sure what you guys changed.
Several people are reporting a problem with ASP.net response.redirect here: http://forums.mozillazine.org/viewtopic.php?f=38&t=2234567 Not convinced it is a Firefox bug (it may be or not), but the users are mixing server-side/client-side languages/snippets, so it is difficult to get usable STR from there comments.
Hi, I experience the same issue, maybe this can help : In asp.net, if server side you call Response.RedirectLocation = "yourUrl"; it works with ie8/9, chrome, FF4 and FF3.6. Using FF5, nothing happens. I'm new to bugzilla, sorry if I posted the wrong way...
We're seeing this problem too on some custom code. The problem seems to boil down to a difference between FF5 and previous versions regarding the existence of a.click where a is an anchor tag. The difference in behaviour can be seen with this simple HTML: <a id="link" href="http://www.google.com" onclick="if (this.click) alert('click'); else alert('no click'); return false">The link</a> Clicking on the link in FF 3.6.18 alerts with "no click" whereas in FF 5 it alerts with "click". The code example above they are testing for (a.click) and calling tmp.click() if found. Other browsers (IE in particular) will then navigate the anchor as if ther user clicked on it while FF will not.
Hmm, this sounds like Bug 666985/Bug 667632, no? Bug 666604 is about to fix those (hopefully pushed for Resolution in Time for Firefox 6).
Fixed by bug 666604.
so, when do you think this fix will be out???
This is definitely fixed in Firefox 7, and may be fixed in Firefox 6.