Closed
Bug 53470
Opened 24 years ago
Closed 24 years ago
checkForDirectoryListing() called a bunch on every page load
Categories
(Core :: Internationalization, defect, P3)
Tracking
()
People
(Reporter: mikepinkerton, Assigned: law)
References
()
Details
(Keywords: perf)
- load abcnews.com watch the console spew hundreds of: JavaScript strict warning: chrome://navigator/content/navigator.js line 1970: reference to undefined property window._content.HTTPIndex warnings. Now these are harmelss, but they indicate that this js routine is being called hundreds of times. Is that correct? It seems like this is something that should only be called once, and has page loading speed impacts.
Reporter | ||
Comment 1•24 years ago
|
||
maybe this is benign, but i don't see how....
Comment 2•24 years ago
|
||
Reassign to law@netscape.com, do you have any idea? This is the code you wrote for me to work around the directory listing problem.
Assignee: nhotta → law
Bill, investigate this and bug #51211, please. Isn't this for someone in the DOM group to fix? I'm inclined to minus this for beta but we should investigate the performance impact before rtm.
I suspect *all* the load listeners are being called (not just checkForDirectoryListing). It just happens that you see that one 'cause of the strict JS thingy. Bug 51211 seems to address the problem of those load listeners getting called for every image load. I'm making this a dup of that one. I'll also go update that one so the discussion of whether/how we fix it for PR3 moves over to there. *** This bug has been marked as a duplicate of 51211 ***
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
Whiteboard: [NEED INFO]
You need to log in
before you can comment on or make changes to this bug.
Description
•