|
|
Posted by Tim Streater on 11/12/07 20:44
In article <1194893219.052938.123110@i13g2000prf.googlegroups.com>,
Andy Dingley <dingbat@codesmiths.com> wrote:
> On 12 Nov, 15:56, Tim Streater <tim.strea...@dante.org.uk> wrote:
> > In article <1194880439.017332.232...@d55g2000hsg.googlegroups.com>,
> > 1001 Webs <1001w...@gmail.com> wrote:
> >
> > > Neither XHTML nor JavaScript are required to design websites nowadays.
> >
> > OK, so how do I do data validation based on user input?
>
> It's not a _requirement_. You can still do it purely server-side,
> which you ought to support as a fallback anyway for both security and
> accessibility reasons.
Of more importance, actually, is the second question I asked, about
modifying one <select> based on the results of another. In some cases I
use Javascript all by itself, when the contents of the select are
limited to a few values, and if, for example, the user choosing "A" in
<select> 1 means they must be prevented from choosing "B" in <select> 2.
Where I really need to restrict the contents of another <select> I put
it in an iFrame, which is passed the results of <select> 1 and then
displays <select> 2. I still have to use javaScript to ensure that the
iFrame <select> is passed a useful parameter and so displays right
subset of values.
My app simply doesn't scale without this sort of technique.
Which is why I complain when I see blanket statements like "JavaScript
is not required to design websites these days".
Navigation:
[Reply to this message]
|