Closed
Bug 265190
Opened 20 years ago
Closed 20 years ago
if size of the JS file is more than about 500 lines mozilla load it improperly - just cut the file??
Categories
(Other Applications Graveyard :: Venkman JS Debugger, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 229024
People
(Reporter: mietekb, Assigned: rginda)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5) Gecko/20031007 Build Identifier: ALL ABOVE ==>> Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5) Gecko/20031007 if size of the JS file is more than about 500 lines mozilla load it improperly - just cut the file?? The situation takes place at all mozilla versions above 1.5. Debugging is impossible, because most functions in files having about 1000-5000 lines are not loaded..I (and all my friends working with me) have to use mozilla 1.5 to debug or use other debuggers. Reproducible: Always Steps to Reproduce: 1. 2. 3.
Related to bug 225708?
| Reporter | ||
Comment 2•20 years ago
|
||
Very similar but I think no the same. I use in my web-application more than 50 files having more than 10kB. Some of them have about 200-300kB. Every file is loaded when the application starts, but few of them dynamically. Problem takes place with every big file. On the list of functions I see a lot of 'undefined' positions, but the count of them is the count of functions in a specified file. I think the problem is more complex than described in bug 225708. But what is very interesting the Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5) Gecko/20031007 is allright. Newer have the problem. I also use Mozilla 1.62 and 1.7a.
Comment 3•20 years ago
|
||
fixed for mozilla 1.7 > 1.7a. why are you testing this in an alpha version, if I may ask? *** This bug has been marked as a duplicate of 229024 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
Updated•20 years ago
|
Product: Core → Other Applications
Updated•6 years ago
|
Product: Other Applications → Other Applications Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•