Strange problem this, None of my update panels are working in IE7. They work fine in Firefox and firebug cannot find any errors on the pages. In IE7 everytime it should update the panel the whole page refreshs. Any ideas why? /emoticons/idea.gif
I always test Ajax in IE7 and FireFox until it works the same in both. At times there are tricks to make it work properly in IE7. Give me a few simple details and I'll try to spill a few of those tricks. btw, IE7 or IE8 in IE7 emulate mode? Reason I ask is, even in IE7 mode the Ajax panels are freaking out in the current beta.
There are not much details. Basicially, I am using an update panel. I have a scriptmanager in my masterpage and I think all the settings are correct in web.config. It was working about a month or less ago but since then I test in firefox, yesterday I noticed it did not work in IE7 (IE7 and not the IE8 beta). It still works fine in firefox. Oh, and I get an error that says 'Access is denied'. A google search keeps bring up results regarding the ajax beta for asp.net 2.0 or if your using frames. I am using neither. ASP.Net 3.5 using the Ajax controls that shipped with it. /emoticons/cry.gif
not sure if this helps, but when i try to test it locally it says 'client-side ajax failed to load'.......online simply says 'access is denied'.
Update! I found this line of code was causing the problem: I use this because, without it, my url rewriting breaks the css! Any ideas how I can fix either this, or redo my references to all css to work? Ideally i way to define where the asp files should be....
The only thing I can think of that I found to help was adding this to your pages using master pages: <%@ MasterType VirtualPath="~/MasterPage.master" %> In that example themaster page is in the site root. i.e.
To the pages where the css is broken or the ajax? If I take out the base url, css breaks for url rewritten pages, if i keep it in Ajax breaks in IE7 Weird weird
If you're having trouble with the Ajax and CSS run tests with the references in the master page and then in the code pages. You can indeed see problems both ways, ajax master page or a root master page with ajax references in the nested pages.
