Like I said in my frist response; I'm probably splitting hairs too much. My point was simply that if you take a normally developed ASP.Net website where the developer doesn't specifically plan for browsers lacking javascript, and someone surfs there with
a browser that is javascript *capable* but javascript *deactivated* then the postback functionality will not work properly. While that doesn't always matter, I've worked in domains where it does. What you're describing relies on detecting browser capabilities,
not browser settings. I understand what you're saying, though, and I really wasn't trying to spawn a debate, merely make the point that javascript is prevalent in ASP.Net whether you use Ajax or not.
Help those who have helped you... remember to "Mark as Answered"
paul.vencill
Contributor
6716 Points
1358 Posts
Re: Why not support post-backs?
Apr 08, 2008 03:21 PM|LINK
Like I said in my frist response; I'm probably splitting hairs too much. My point was simply that if you take a normally developed ASP.Net website where the developer doesn't specifically plan for browsers lacking javascript, and someone surfs there with a browser that is javascript *capable* but javascript *deactivated* then the postback functionality will not work properly. While that doesn't always matter, I've worked in domains where it does. What you're describing relies on detecting browser capabilities, not browser settings. I understand what you're saying, though, and I really wasn't trying to spawn a debate, merely make the point that javascript is prevalent in ASP.Net whether you use Ajax or not.