On 8/31/2010 10:54 AM, Ken wrote: > On Aug 31, 9:45 am, "David E. Ross" <[email protected]> wrote: >> Is your server sniffing for "Firefox"? It should instead sniff for >> "Gecko". >> >> However, if you make your site compliant with the W3C specifications, it >> is likely that you do not have to sniff at all. >> >> For an explanation of sniffing, see my >> <http://www.rossde.com/internet/Webdevelopers.html#sniff>. > > > I don't think "sniffing" is the issue we're running into. We are > checking the user agent but it's only to limit the browsers that can > access the site period, not to serve up different content based on the > browser used. > > What is happening is that the script resources and hidden fields used > by asp.net ajax are not getting registered on the page when we run the > app in the 4.0 version of the .NET Framework. Everything works great > running under the 3.5 version though. The only real difference is that > for the 4.0 version is that there are some sections removed from the > web.config file and are supposed to be used from the machine.config. > For some reason, SeaMonkey just isn't getting it.
Ken, If you're building the web site with a tool like Microsoft VS.NET, are you sure it is not doing any sniffing? To be sure, try changing the user agent string sent by SeaMonkey to that normally sent by Firefox and see what happens. If the application begins working, it's a sniffing issue. Good luck. _______________________________________________ support-seamonkey mailing list [email protected] https://lists.mozilla.org/listinfo/support-seamonkey
