Closed
Bug 91881
Opened 23 years ago
Closed 23 years ago
javascript error in cookieTasksOverlay.xul
Categories
(Core :: Networking: Cookies, defect)
Core
Networking: Cookies
Tracking
()
VERIFIED
FIXED
mozilla0.9.4
People
(Reporter: bugzilla, Assigned: morse)
References
Details
Attachments
(6 files)
788 bytes,
patch
|
Details | Diff | Splinter Review | |
3.47 KB,
patch
|
Details | Diff | Splinter Review | |
3.45 KB,
patch
|
Details | Diff | Splinter Review | |
1.30 KB,
patch
|
Details | Diff | Splinter Review | |
1.31 KB,
patch
|
Details | Diff | Splinter Review | |
667 bytes,
patch
|
Details | Diff | Splinter Review |
Start the console and from within the console select: Tasks -> Privacy -> Cookies -> Unblock from this site you'll get: Error: window._content has no properties Source File: chrome://cookie/content/cookieTasksOverlay.xul Line: 80 If you select Tasks -> Privacy -> Cookies -> Block from this site You'll get: Error: window._content has no properties Source File: chrome://cookie/content/cookieTasksOverlay.xul Line: 85
Comment 1•23 years ago
|
||
This looks to be a dup of bug 74541. Henrik, I notice you filed both -- is this something different?
Assignee | ||
Comment 2•23 years ago
|
||
Bug 74541 was a double bug referring to errors at lines 57 and 85. Furthermore, it gave no steps to reproduce. Henrik has since clarified that bug report with the necessary reproduce steps, but only for the line 57 bug (althought I cannot reproduce it using the steps he gave). This report is for the line 85 bug. This shows the importance of not combining two bugs in one report. The line 57 bug I am unable to reproduce and so have marked bug 74571 as works for me. The line 80/85 bug as described here I can reproduce and am currently investigating and will eventually fix it and close this report out as fixed. If this was all in one report, I would not know whether to close the report out as fixed or as works-for-me.
Status: NEW → ASSIGNED
Target Milestone: --- → mozilla0.9.3
Assignee | ||
Comment 3•23 years ago
|
||
Oops, I meant 74541 above, not 74571.
Assignee | ||
Comment 4•23 years ago
|
||
Assignee | ||
Comment 5•23 years ago
|
||
vishy, blake, please review. thanks.
Assignee | ||
Comment 6•23 years ago
|
||
Actually a better thing to do is to remove the cookie/image items from the tasks->privacy menu when in the javascript console. Attaching a patch that does that. If we don't remove the items from the menu, but rather attempt to fix all the places where problems will occur when in the javascript console, we quickly get into trouble. Specifically, we don't know whether or not to hide the imageblocking menu items since that is controlled by a pref and we can't test check the prefs when in the javascript console.
Assignee | ||
Comment 7•23 years ago
|
||
Assignee | ||
Comment 8•23 years ago
|
||
Comment 9•23 years ago
|
||
I am still confused as to why we can't check the prefs when we open the Tasks menu.
Comment 10•23 years ago
|
||
I'm not convinced that we should make the tasks menu be different in the JavaScript Console (I'm not sure that why the menu is there to begin with in the JS console but thats a different question). I'd rather if we fixed the errors than removed the menu items. German - is there any invariant that the Tasks menu has to be same everywhere?
Assignee | ||
Comment 11•23 years ago
|
||
We can't fix the underlying problem as I already described. We keep running into the following brick wall: 1. Image manager is to appear in commercial product if pref is set 2. Testing a pref works from the browser window but not the js console 3. Therefore browser window can test pref and determine if image manager menu items are to be displayed 4. Testing a pref does not work from js-console window 5. Therefore js-console window cannot determine whether or not it should display the image manager menu items. 6. Therefore it is not possible to have same taskmenu display in both browser window and js-console window.
Comment 12•23 years ago
|
||
I cannot find where you explained why we are unable to test the pref from the js console. Reading the original bug, I agree that the block/unblock items should be removed, but not all of the items.
Assignee | ||
Comment 13•23 years ago
|
||
Problem is that this.pref doesn't exist when in js-console window. So it requires additional code to obtain the pref. Attaching new patch that does this. But I still think that its wrong to have the ability to block cookies, bring up cookie tutorial, etc from the javascript console. Taking it one step further, it's wrong to have any task menu there at all. But assuming that we have to have it, then this is as good a patch as any.
Assignee | ||
Comment 14•23 years ago
|
||
Comment 15•23 years ago
|
||
r=vishy on this patch. I think we shd revisit why the Menu is there for JS console after m0.9.4, when eMojo has branched.
Comment 16•23 years ago
|
||
+ var pref; + pref = Components.classes['@mozilla.org/preferences;1']; + pref = pref.getService(); + pref = pref.QueryInterface(Components.interfaces.nsIPref); + if (!pref.GetBoolPref("imageblocker.enabled")) { I believe the new way is to use nsIPrefBranch. Also, need to null check pref or leave it in the try/catch... + if (!window._content) { I think this will cause a strict warning (or maybe just an error). How about if ("_content" in window)? sr=blake
Assignee | ||
Comment 17•23 years ago
|
||
Assignee | ||
Comment 18•23 years ago
|
||
Fix checked in.
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 19•23 years ago
|
||
hmmm did this really get checked in? I'm still seeing the js error... build 20010811 Error: window._content has no properties Source File: chrome://cookie/content/cookieTasksOverlay.xul Line: 93 Error: window._content has no properties Source File: chrome://cookie/content/cookieTasksOverlay.xul Line: 103
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Assignee | ||
Comment 20•23 years ago
|
||
Assignee | ||
Comment 21•23 years ago
|
||
cc'ing blake and matt for reviews
Assignee | ||
Updated•23 years ago
|
Status: REOPENED → ASSIGNED
Target Milestone: mozilla0.9.3 → mozilla0.9.4
Comment 22•23 years ago
|
||
sr=blake
Comment 23•23 years ago
|
||
r=matt
Assignee | ||
Comment 24•23 years ago
|
||
fix checked in
Status: ASSIGNED → RESOLVED
Closed: 23 years ago → 23 years ago
Resolution: --- → FIXED
Comment 25•23 years ago
|
||
verified: WinNT 4 2001-09-20-11-0.9.4 Mac os9 2001-09-20-12-0.9.4 Linux rh6 2001-09-20-17-0.9.4
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•