Closed Bug 284467 Opened 20 years ago Closed 19 years ago

non critical halt or crash when javascript submit () in sequence with parent javascript function call

Categories

(Firefox :: General, defect)

x86
Windows 2000
defect
Not set
critical

Tracking

()

RESOLVED EXPIRED

People

(Reporter: dreaddy_mck, Assigned: bugzilla)

Details

(Keywords: crash)

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0

I have a parent document with an iframe embeded in a table
Parent document contains a javascript function that utilizes style.display to
hide a table and resize the table containing the iframe.
The parent javascript function is called from the iframe

parent javascript:
	function toggle_mid_display(val)
	{
		var ifrm_container	= document.getElementById('search_display');
		var curr_container	= document.getElementById('current_display');
		if(val) {
			curr_container.style.display	= 'none'
			ifrm_container.height 			= 500;
		}else{
			curr_container.style.display	= 'inline'
			ifrm_container.height 			= 200;
		}
		return;
	} 


iframe javascript

	function whatever() {
		var obj 		= document.search_form;

		if(!obj.key_words.value) {
			alert('Please Enter a Keyword');
			obj.key_words.focus();
			return false;
		}else{
                        parent.toggle_mid_display(1);
			obj.command.value = "search";
			obj.submit();			
			return true;
		}
	}

	</script>

the iframe script calls the parent function fine, but halts or crashes on the
submit. This then requirs a second click on the submit button to complete the
process.

Reproducible: Always
Do you have a talkback ID for that crash (or a Test URL ?)
Severity: normal → critical
Keywords: crash
by crash, do you mean that all browser windows close?
No, bad choice of words. 
What I mean is: All the javascript commands execute successfully except the submit
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.