173879 - Javascript error: uncaught exception while opening View Page/Selection Source

Status: VERIFIED FIXED

(Firefox :: General, defect)

Description

[Adam Hauner]

20021010/W2K

Repro:
1. go to http://www.mozilla.org/
2. open Page Source

Actual (in JS console):
Error: uncaught exception: [Exception... "Component returned failure code:
0x8000ffff (NS_ERROR_UNEXPECTED) [nsIPrefBranch.getIntPref]"  nsresult:
"0x8000ffff (NS_ERROR_UNEXPECTED)"  location: "JS frame ::
chrome://cookie/content/cookieTasksOverlay.xul :: <TOP_LEVEL> :: line 88"  data: no]

Expected:
Without errors.

(Actual Mozilla trunk nightbuild hasn't this error.)

Comment 1

[Blake Ross]

Is this still happening?

Comment 2

[Adam Hauner]

Yep, I'm getting same error with actual 20021104/W2K Phoenix build.

Comment 3

[david.butts]

Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.3a) Gecko/20021112 Phoenix/0.4
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3a) Gecko/20021112 Phoenix/0.4

Both generate the same error, (though referring line Error: uncaught exception: 

[Exception... "Component returned failure code: 0x8000ffff (NS_ERROR_UNEXPECTED)
[nsIPrefBranch.getIntPref]"  nsresult: "0x8000ffff (NS_ERROR_UNEXPECTED)"
location: "JS frame :: chrome://cookie/content/cookieTasksOverlay.xul ::
CookieTasksStartup :: line 84"  data: no]

Comment 4

[Asa Dotzler [:asa]]

We should probably set the pref that hides chrome JS errors in the JS console
for our releases. Even among the small subset of users that look at the JS
console, very few of them care about application errors. 

Comment 5

[eric lindvall]

Attachment: Patch to catch exception

I'm not sure if this bug was meant to be a general bug to fix all problems like
this, or specifically fix this exception, but here is a patch that catches the
specific exception that is being thrown.

Comment 6

[Erik]

*** Bug 207111 has been marked as a duplicate of this bug. ***

Comment 7

[Blake Ross]

This will go away when we have our own view source. I believe pch is working on
issues like this.

Comment 8

[Simon Paquet [:sipaq]]

*** Bug 218286 has been marked as a duplicate of this bug. ***

Comment 9

[Steffen Wilberg]

*** Bug 219579 has been marked as a duplicate of this bug. ***

Comment 10

[Bill Mason]

*** Bug 219885 has been marked as a duplicate of this bug. ***

Comment 11

[Pierre Chanial]

fixed.

Comment 12

[Steffen Wilberg]

The javascript error is gone. -> verified.