Closed Bug 261099 Opened 20 years ago Closed 20 years ago

Running an applet in one tab makes form entry fields in another tab unresponsive

Categories

(Firefox :: Tabbed Browser, defect)

PowerPC
macOS
defect
Not set
normal

Tracking

()

VERIFIED DUPLICATE of bug 162134

People

(Reporter: C.Voelker, Assigned: bugs)

References

()

Details

User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.3) Gecko/20040913 Firefox/0.10 Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.3) Gecko/20040913 Firefox/0.10 I opened the Applet mentioned in the URL above and used it once or twice to calculate income taxes. Then I opened another Site http://www.banktip.de/gehaltsrechner.asp in a new tab in the same window. This Site does not use an applet but a serverside calculation based on a plain simple html form. I could not delete default values from entry fields nor enter new values. I am not sure whether this one is connected with the problem described here but it took several tries to copy the URL from the address field. I clicked into the address field once. The whoile address became highlighted. I hit Command-C, then switched to this window to paste the URL into the description and found the former content of the clipboard to be pasted. Doing the same another time but using menu commands this time worked allright. To find out about reproducability I closed the tab with the applet. Then, the form worked as expected. I opened the other Site again in a new tab within this window and switched back to the form which was still working fine. Switching to the applet and using it once, then switching back to the form it stopped working again. Reproducible: Always Steps to Reproduce: 1. open http://www.nettolohn.de/ 2. create a new tab and open http://www.banktip.de/gehaltsrechner.asp 3. use the latter one for a calculation and see that it works fine 4. switch to the first one and make another calculation and see that it works 5. switch back to the second tab (www.banktip.de/...); try to enter new values Actual Results: I could not enter my values for calculation into the form nor could I delete old values with backspace. I could highlight the text using the mouse but I could not remove it. This is true for text entry fields only, not for drop lists or radio buttons. Expected Results: The form should have worked ordinarily. Also, switching back and forth between both tabs showed some drawing errors. Sometimes I could still see parts of the Applet when I had switched to the form.
Working on Windows Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20040913 Firefox/0.10 If I remember I will give a shot at reproducing this bug on an OS X machine that I administrate.
This looks like a duplicate of bug 162134
Hello, I agree, this is probably related to bug 162134 which is a megabug with 120 additions or so, phew. I sware, I have searched for bugs before opening one myself but I searched only bugs files for Firefox, so I havent found it. As there were other comments on this bug existing in Firefox too, Id suggest, not to remove it entirely so that others searching Firefox only can see the cross reference to bug 162134. Also, let me emphasize that the combination of an applet and a form gives this bug a new quality because there is not only visual impact but functional impact too. Actually I did not get a visual clue of the applet running berserk. I had not even noticed that it was an applet because it loaded really fast. I found out only when thinking about the form not working. I could not reproduce this behaviour with the applet mentioned in the URL of bug 162134. when opening this in another tab besides this form, I saw the applet dancing on the wrong tab but form fields were still accessible as ususal. This is why I think that the URLs I mentioned are still valuable additions for testing a fix to this bug. Bye, Christian *** This bug has been marked as a duplicate of 162134 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.