Closed
Bug 252986
Opened 20 years ago
Closed 20 years ago
Javascript from one site keeps running after selecting another tab using multiple tabs.
Categories
(Firefox :: Tabbed Browser, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 104532
People
(Reporter: tenty, Assigned: bugs)
References
()
Details
Attachments
(1 file)
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7) Gecko/20040707 Firefox/0.9.2 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7) Gecko/20040707 Firefox/0.9.2 Using the URL in the URL field, (http://www.serials.ws/all/?l=N&pn=2 yes I know it's a cracks site) if you open that URL, then open a new tab and go elsewhere, the javascript which controls the ticker at the bottom of the screen continues to run on any current tab you are on including the serials tab. It doesn't seem to matter if you have 2 or 9 tabs open (I chose 9 because thats how many I have open), the ticker continues to run. Reproducible: Always Steps to Reproduce: 1. open Firefox 0.92 2a. open a website (ie. google) OR 2b. go to the website with javascript ticker If you chose 2a, goto 3a: 3a. goto website with javascript ticker, like the one mentioned in the URL field and then click on the tab with your website (ie google) OR 3b. open a new tab and goto a website of your choice, ie google. Optional: 4. open a second/third/fourth/etc tab and goto a new website OR click on an existing open tab. The javascript ticker is not contained in the tab. Actual Results: If you use the serials website, you shoudl see a ticker at the bottom of the scrren which says: "Serials - www.serials.ws" which types itself out and then scrolls to the left deleting the words. Expected Results: I believe the ticker should be self contained to the one and only tab that started it. I don't know how many other javascript problems this may cause.
Comment 2•20 years ago
|
||
*** This bug has been marked as a duplicate of 104532 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•