Closed Bug 219322 Opened 21 years ago Closed 21 years ago

Mozilla downloads JavaScript even when JavaScript is turned off

Categories

(Core :: JavaScript Engine, defect)

x86
Linux
defect
Not set
normal

Tracking

()

VERIFIED DUPLICATE of bug 66857

People

(Reporter: sandreas41, Assigned: rogerl)

References

()

Details

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030727
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030727

Regardless of if JavaScript is turned on or not (via preferences), Mozilla
always downloads JavaScripts external to the HTML page being loaded.

Reproducible: Always

Steps to Reproduce:
1. Erase the cache directory (before starting Mozilla). (optional)
2. Load Mozilla.
3. Turn off JavaScript in the Advanced Scripts & Plugins preferences page
("Enable JavaScript for"..."Navigator").
4. Go to a page that uses external JavaScripts (like the one referenced).
5. Note that the browser connects to another server for the JavaScript.  (In
this case, an ad server).
6. Close Mozilla when the page has loaded.
7. Check the cache directory's contents.

Actual Results:  
Mozilla loaded an ad JavaScript when no JavaScripts were being run ("Enable
JavaScript for"..."Navigator" was off) and placed the JavaScript downloaded into
the cache.

As a side note, it slows down my MODEM transfers and delays the display of the
page until it gets the JavaScript.  Add in sloooow DNS lookups for the server
hosting the JavaScript... and (often) a slow JavaScript-hosting server...  Eeek.


Expected Results:  
It should not have loaded the referenced JavaScripts -- why would I want to
download JavaScripts when I'm not going to do anything with them?
dupe of "disabling javascript still loads javascript into cache."

*** This bug has been marked as a duplicate of 66857 ***
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
Marking Verified Duplicate.

However, I'm a little puzzled by the dates here. Bug 66857 was
marked Fixed on 2003-07-24, yet sandreas41@yahoo.com's build id
is 20030727. 

sandreas41@yahoo.com: could you try a current build (2003-09-xx)
and see if the problem still exists? If so, please re-open
bug 66857. This is not a JavaScript Engine issue; thanks -
Status: RESOLVED → VERIFIED
> However, I'm a little puzzled by the dates here. Bug 66857 was
> marked Fixed on 2003-07-24, yet sandreas41@yahoo.com's build id
> is 20030727. 

it was only FIXED-on-trunk.  reporter was using a 1.4 build.
You need to log in before you can comment on or make changes to this bug.