Comments on: OSCON 2006: Ajax + .NET = Atlas

By: Ahmet Kaymaz

Ahmet Kaymaz — Mon, 30 Oct 2006 19:54:25 +0000

I make textbox disabled=true in client side. Then, when I get to the server in post action, these objects lose their value.

Ahmet Kaymaz
Asp.Net,C#, VB.NET, SQL, Oracle,SQL Server 2005

By: n

Mon, 31 Jul 2006 21:09:37 +0000

ASP.NET applications do no fail to work with javascript disabled.

Some functionality will fail, but if you understand what is happening under the hood and you want to make it right - you can.

You can build an application on asp.net which one need anything but plain html, it will just take a bit of manual labour and knowledge.

By: chris ward

chris ward — Sun, 30 Jul 2006 14:26:49 +0000

Wenz then went on to build a simple autocomplete demo in the same vein as Google Suggest. This was surprisingly easy to do, thanks to Atlas’s ability to extend existing ASP.NET components (like the TextBox) with AJAX functionality. I was gratified to see that this degraded gracefully back to a plain TextBox when JavaScript was disabled on the client side.

Yes, the ATLAS-enabled textbox will degrade gracefully, but still…
ASP.NET applications fail to work with Javascript disabled.

This is due to the way they’ve used javascript to handle the way they post forms to the server.
I really wish they’d fix this.