Hi again... finally got back to this. Here are a few clarifications:
1) the use of "var xyz = new Object(someOtherObject)" was a workaround, probably dating to IE6 or earlier. I'd found that in some cases, objects passed as method arguments and then assigned to a variable would yield "object...
The pages using this framework use event handlers to manage validation and submittal; some pages use a hidden form for the actual submittal, in which case the form the user completes has no action attribute, so a form-level onSubmit() handler is inappropriate. The user form's buttons have an...
Instead of depending on x going out of scope, try explicitly releasing it:
...
x.send(null);
x = null;
...
If nothing else it will at least get collected sooner (maybe). As it is now, it doesn't go out of scope until the timeout expires.
I agree with Feherke, who must have a web security background ;-)
I see "cgi" in the URL there, which in the old days meant standalone executables for each page, but I assume you're actually using a framework. Can you comment on which framework you're using, and on whether that framework...
Martin,
I'm not sure what you mean by the "Apache userid", which taken literally would be the user account under which the server is running. I really don't think you want to expose that!
Assuming you meant the "userid" of the client on the browser, you *may* be able to get the value from one...
I'd take Jason's a step further: use two forms, one with a "search by ID" button and the other with "search by Name" button, where each button is positioned directly below the relevant input fields. This should make it clear which of the field(s) the user should fill in without having to provide...
You can use hidden forms to accomplish the same thing. The links would have an onClick() that invokes a function to populate the hidden form's fields with the values you want to pass.
For example, assume you want to link to a help facility and every page sets a 'currentPage' variable. Then,
*...
Code spanning multiple lines shouldn't be an issue as long as you don't split in the middle of an object, method or property name. It can make the code more readable, and help in spotting errors.
You didn't say in what way the code "doesn't work", but I see several issues. First, be aware that...
I have a classic ASP site I maintain for a friend, part of which consists of a framework providing a "wizard" interface with navigation buttons (i.e., "Next" and "Previous"). The buttons have the same name and id of 'navButton', and have an onClick() event that invoke a function to perform some...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.