Closed Bug 200305 Opened 23 years ago Closed 21 years ago

In <navigator.js>, JS "Error: popupManager.getEnumerator is not a function". (on clicking "OK" after changing the 'Block unrequested popup windows' checkbox value)

Categories

(SeaMonkey :: Preferences, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 221232

People

(Reporter: sgautherie, Assigned: shliang)

References

Details

Attachments

(1 obsolete file)

User-Agent: Mozilla/5.0 (Windows; U; Win95; en-US; rv:1.4a) Gecko/20030401 Build Identifier: Mozilla/5.0 (Windows; U; Win95; en-US; rv:1.4a) Gecko/20030401 This one appeared between v1.3 and v1.4a !? Reproducible: Didn't try Steps to Reproduce: (I am not sure of what triggered this error.) Actual Results: [ Error: popupManager.getEnumerator is not a function Source File: chrome://navigator/content/navigator.js Line: 171 ] PS: *Is there any meta-bug to block for all the Chrome js error bugs around ? *Theses bugs do not seem to create any trouble, except they all clutter the JS.C. output, thus it's quite difficult to find "real" problems.
> except they all clutter the JS.C. output There's a preference for this; distributors who want to (eg Netscape) can turn it off. shliang, this error sounds like something you'd know about...
Re comment 1: I assume that you think about 'Debug > Show chrome JavaScript errors and warnings' UI. Additions to my Description: *"meta-bug to block for all": I meant to use it as a tracker in Bugzilla, to enhance visibility. *"all clutter the JS.C.": I wanted to point out that unlike (at this point) this bug which seems new, there are a few longstanding ones which clutter ... while looking for new (chrome) ones.
reassign
Assignee: asa → shliang
Status: UNCONFIRMED → NEW
Ever confirmed: true
Attached patch patch (obsolete) — — Splinter Review
the popup pref listener wasn't changed to reflect recent changes to permissions, but those lines aren't needed anymore anyway because we don't support blacklists anymore
Attachment #119216 - Flags: superreview?(jaggernaut)
Attachment #119216 - Flags: review?(danm)
Comment on attachment 119216 [details] [diff] [review] patch sr=jag
Attachment #119216 - Flags: superreview?(jaggernaut) → superreview+
Attachment #119216 - Flags: review?(danm) → review+
Will the patch land for v1.4f, or may be in v1.5a ?
Will this land before 1.5 final? A few duplicates of this have been found: 208090 and 189869
*** Bug 208090 has been marked as a duplicate of this bug. ***
[Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.4) Gecko/20030624] (W98SE) See bug 208090 description for reproductible testcase: the error happens on clicking "OK" after changing the checkbox value. Code location in current trunk is <http://lxr.mozilla.org/seamonkey/source/xpfe/browser/resources/content/navigator.js#172>. Bug happens on W95B (description), W98SE (this comment), W2K (bug 208090). Changing: *(Component) Browser-General -> Preferences *(OS) W95 -> W98 [since I upgraded eventually :->] Asking for 'blocking1.4.x', since there is an approved patch waiting for landing for months.
Component: Browser-General → Preferences
Flags: blocking1.4.x?
OS: Windows 95 → Windows 98
Re comment 7: I checked your bug 189869 comment 4; but I guess that that bug is unrelated to this bug, is it not !?
The javascript attached in bug 189869 causes "popupManager.getEnumerator is not a function" to appear in the Javascript Console. I had thought that fixing the popup error would resolve the bug with the Javascript and allow the popup window to appear. I could be wrong on that.
Re comment 11: I believe you're right (not wrong); but see my bug 189869 comment 5: I would be ready to add "blocks: 189869"; but I didn't find any clue about this in that other bug yet... (I'd like to experience it myself before acting)
Flags: blocking1.4.1? → blocking1.4.1-
[Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.5b) Gecko/20030827] (W98SE) Line number update: 171 -> 172 { Error: popupManager.getEnumerator is not a function Source File: chrome://navigator/content/navigator.js Line: 172 } (Shliang) Still noone to land your 2reviewed patch ??
Summary: In <chrome://navigator/content/navigator.js>, JavaScript "Error: popupManager.getEnumerator is not a function" → In <chrome://navigator/content/navigator.js>, JavaScript "Error: popupManager.getEnumerator is not a function". (on clicking "OK" after changing the 'Block unrequested popup windows' checkbox value)
QA Contact: asa
Patch has bitrotted; do we still see this error?
Repro from bug 208090 WFM - 2004011308/trunk/W2K
[Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.6b) Gecko/20031208] (W98SE) WorksForMe confirmed :-) The code was changed in: (bug 221232 is duplicate of current bug !) { 1.520 mvl%exedo.nl Oct 31 2003 nsIPopupManager.getEnumerator is replaced by nsIPermissionManager.getEnumerator bug 221232, r=dwitte, sr=bryner } Still, in comment 4, shliang wrote { those lines aren't needed anymore anyway because we don't support blacklists anymore } jag: Should I update the patch to remove these lines !?
Depends on: 221232
Product: Browser → Seamonkey
Neil: Could you help answering comment 6 ?
OS: Windows 98 → All
Hardware: PC → All
Summary: In <chrome://navigator/content/navigator.js>, JavaScript "Error: popupManager.getEnumerator is not a function". (on clicking "OK" after changing the 'Block unrequested popup windows' checkbox value) → In <navigator.js>, JS "Error: popupManager.getEnumerator is not a function". (on clicking "OK" after changing the 'Block unrequested popup windows' checkbox value)
Whiteboard: [Related issue remains: see comment 16]
Maybe mvl knows, or maybe we should just resolve this bug as dup of 221232
The answer to comment 6 is ofcourse 6, given that it didn't happen. And there isn't anything we can do to change that. If you mean comment 16, that would be a new bug. The bug as reported here is fixed. *** This bug has been marked as a duplicate of 221232 ***
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
No longer depends on: 221232
Attachment #119216 - Attachment is obsolete: true
(In reply to comment #19) > If you mean comment 16, that would be a new bug. The bug as reported here is fixed. Yes, I meant comment 16 :-/ I thought this bug could have been morphed; anyway, I filed bug 279479 !
Whiteboard: [Related issue remains: see comment 16]
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: