RE: Is or isn't scripting needed, was RE: XForms vs. Web Forms

>To use its full functionality, you do need a new browser.  However, the
>same WF2 content still works in old browsers.  It just doesn't take
>advantage of the new features.
>It's preferable because authors can start using the new features and
>providing the benefits of those features to users even when a
>significant portion (even a majority) of the users don't have a browser
>that supports WF2.  This situation would allow the deployment of WF2 to
>provide an incentive for users to upgrade their browsers, since the
>pages will work *better* in the new browsers.

While 'ignore what you do not understand' allows the pre-forms web
markup
to fail gracefully, it is a common misconception that this idea can
transfer
to the forms space.

It can't.

If you get an html page sans images, you can still make a lot of sense
of 
content just with the text, but if you write a form that is designed to
present 
a shopping cart to the user, it either presents the repeating rows or it
doesn't.  
There is no notion of "mostly working" with forms.  It's either working
or its "mostly broken."

John Boyer, Ph.D.
Senior Product Architect and Research Scientist
PureEdge Solutions Inc.

Received on Thursday, 17 March 2005 01:01:11 UTC