Sounds little confusing ? Well testcase will be self explanatory. If we try to set childWindow.opener = self; & if we are incrementing some other JS variable value, its not getting incremented. This blocks automation testing process. BUILDS: XPCDOM STEPS TO REPRODUCE: 1] Please download zip file I'm going to attach. [Two testcases] 2] Extract both in same directory. 3] file 'ggg2.html' is main file. open this file using xpcdom builds. 4] click button "Open new win". 5] you will see infinite alerts with JS variable "tcnum = 0". [Kill this proces somehow. "holding Return-key on keyboard & Clicking window exit icon at same time"] 6] Now open the source code of "ggg2.html" & comment line "testWin.opener = self;" 7] Now try again steps 3 & 4. 8] Now you will see 4 alerts with JS variable "tcnum" incrmenting its value on every alert by 1. [This is what is supposed to happen.]. EXPECTED RESULTS: You should see 4 alerts in entire process showing 'tcnum = 0', 'tcnum = 1', 'tcnum = 2', 'tcnum = 3' ACTUAL RESULTS: You see infinite alerts showing 'tcnum = 0', ..............[you have to kill the process somehow] THIS IS AUTOMATION BLOCKER. testcase attachment to follow.
I said I will be attaching zip file. Instead I attached two HTML files "Two files for one complete testcase". "ggg2.html" is main file & "ggg3.html" is child window file.
Summary: xpcdom :- setting childWindow.opener = self; forces JS variables not to increment its value. → xpcdom :- setting childWindow.opener = self; forces JS variables not to increment its value.
Fond the problem, thanks for the bug.
Summary: xpcdom :- setting childWindow.opener = self; forces JS variables not to increment its value. → [xpcdom] setting childWindow.opener = self; forces JS variables not to increment its value.
Fix checked in on the xpcdom branch.
Status: NEW → RESOLVED
Last Resolved: 18 years ago
Resolution: --- → FIXED
Verified with 2001-05-22-04. xpcdom allready landed in.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.