Closed
Bug 67810
Opened 24 years ago
Closed 15 years ago
javascript strict warnings in navigatorDD.js
Categories
(Core :: DOM: Copy & Paste and Drag & Drop, defect, P4)
Core
DOM: Copy & Paste and Drag & Drop
Tracking
()
RESOLVED
WORKSFORME
Future
People
(Reporter: bugzilla, Assigned: hewitt)
References
Details
JavaScript strict warning: chrome://navigator/content/navigatorDD.js line 108: reference to undefined property aDragSession.sourceElement JavaScript error: chrome://navigator/content/navigatorDD.js line 249: aElement has no properties
Comment 2•23 years ago
|
||
-> xpapps dnd
Assignee: ben → blakeross
Component: XP Apps → XP Apps: Drag and Drop
QA Contact: sairuh → tpreston
Comment 3•23 years ago
|
||
Henrik, can you still reproduce this?
Reporter | ||
Comment 4•23 years ago
|
||
yeps... if you have folders in your personal toolbar. Then try to drag a subfolder of a folder in the personal toolbar to the content area you get: JavaScript strict warning: chrome://navigator/content/navigatorDD.js line 108: reference to undefined property aDragSession.sourceElement JavaScript error: chrome://navigator/content/navigatorDD.js line 249: aElement has no properties build 20010426
Assignee | ||
Comment 7•23 years ago
|
||
these are fixed now
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 8•23 years ago
|
||
I cant see the warnings with todays build 20010619. Will reopen if I see them again. Please add the following line to your prefs.js file, so we could avoid all these strict warning fixup...: user_pref("javascript.options.strict", true);
Status: RESOLVED → VERIFIED
Reporter | ||
Comment 9•23 years ago
|
||
Warning: anonymous function does not always return a value Source File: chrome://navigator/content/navigatorDD.js Line: 255, Column: 18 Please add the following line to your prefs.js file, so we could avoid all these strict warning fixup...: user_pref("javascript.options.strict", true);
Status: VERIFIED → REOPENED
Resolution: FIXED → ---
Assignee | ||
Updated•23 years ago
|
Status: REOPENED → ASSIGNED
Priority: -- → P4
Target Milestone: --- → mozilla1.0
Assignee | ||
Updated•23 years ago
|
Target Milestone: mozilla1.0 → Future
Comment 10•23 years ago
|
||
Reporter: Can you reproduce this in a recent build? I don't see a way to easily reproduce this strict JS warning. Also, looking at the function line 255 of http://lxr.mozilla.org/seamonkey/source/xpfe/browser/resources/content/navigatorDD.js is in, and the two adjoining functions, I do not see anything which would cause this particular strict warning. This bug hasn't been commented on in about 5 months. It could be the above strict warning is no longer valid.
Reporter | ||
Comment 11•23 years ago
|
||
drag a link from a webpage to the Search button and you'll get: Warning: reference to undefined property xferData[1] Source File: chrome://navigator/content/navigatorDD.js Line: 422 Warning: assignment to undeclared variable kNC_Name Source File: chrome://navigator/content/navigator.js Line: 665 Warning: assignment to undeclared variable defaultEngine Source File: chrome://navigator/content/navigator.js Line: 667 20020117
Comment 13•15 years ago
|
||
WFM: Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.9.1b4pre) Gecko/20090305 SeaMonkey/2.0b1pre
Status: ASSIGNED → RESOLVED
Closed: 23 years ago → 15 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•