|
|
Posted by mbstevens on 11/19/51 11:31
Ed Jay wrote:
>>JavaScript, but you still need to test server side because this won't
>>work for every visitor.
> My audience is limited to subscribers to a service and one of the
> conditions is that they must have javascript enabled.
Hmm. So, when people who hate javascript visit, they have to re-set
their browser, and then re-re-set it on leaving. Are you sure that you
really _need_ to require your visitors to use javascript? I once did
banking at a place that required that, and it irritated the hell out of me.
> That said, am I to
> presume a javascript to poll the answers to my two problematic questions
> is what you're suggesting?
Well, I don't know fully what the questions are, but yes, other things
being equal, a JS check will usually work.
>
> Not difficult to do, except that the questions are answered with
> checkboxes or radio boxes and without doing a ton of conditional tests for
> each question, I don't know how else to show the state of each answer box.
Well, you could just generate a page to re-ask the problem question with
the same script, if you wanted.
> As I type this, I just had a thought. Go to Page 2 (or a dedicated error
> checking page) and check for the error. If the error exists, print the
> error message and either use either <a href="javascript:history.back()">
<a href="javascript:history.go(-1);">Back</a>
Doesn't always work, even with JS enabled. You'll also have to require
your subscribers to use their browser's history list, which some people
disable, for instance with security software.
> or a message telling the op to use his browser's 'Back Button' to return
> to Page 1. The complete state is save in the cache.
>
As long as you can already program some in Perl, just do it right and
generate a page with a script to get the information needed. All this
jumping around in javascript sounds a bit kludgy for my taste, but it's
your page.
Navigation:
[Reply to this message]
|