Closed Bug 461552 Opened 17 years ago Closed 17 years ago

about:about is broken on SeaMonkey (trunk)

Categories

(SeaMonkey :: General, defect)

defect
Not set
normal

Tracking

(Not tracked)

VERIFIED INVALID
seamonkey2.0a2

People

(Reporter: tonymec, Unassigned)

References

()

Details

From bug 349451 comment #49: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1b2pre) Gecko/20081024 SeaMonkey/2.0a2pre - Build ID: 20081024000423 Trying to browse to about:about leaves the content area blank, with the following messages in the Error Console: [X] Error: [Exception... "'JavaScript component does not have a method named: "getURIFlags"' when calling method: [nsIAboutModule::getURIFlags]" nsresult: "0x80570030 (NS_ERROR_XPC_JSOBJECT_HAS_NO_FUNCTION_NAMED)" location: "JS frame :: chrome://communicator/content/contentAreaClick.js :: addToUrlbarHistory :: line 262" data: no] Source File: chrome://communicator/content/contentAreaClick.js Line: 262 [X] Error: [Exception... "'JavaScript component does not have a method named: "getURIFlags"' when calling method: [nsIAboutModule::getURIFlags]" nsresult: "0x80570030 (NS_ERROR_XPC_JSOBJECT_HAS_NO_FUNCTION_NAMED)" location: "JS frame :: chrome://global/content/bindings/browser.xml :: loadURIWithFlags :: line 186" data: no] Source File: chrome://global/content/bindings/browser.xml Line: 186 The latter one happens twice. Now I'm going to test a recent tinderbox-build (maybe this nightly didn't include the fix). As I said in bug 349451 comment #50, this happens identically in the 20081024091143 tinderbox-build.
ah, s**t, maybe an extension-related thing: bug doesn't happen in a clean profile. Let me test further...
Disabling MR Tech Toolkit 6.0.1 (which advertises support for SeaMonkey 2.0a1) fixes it. Let's add a comment on the Mozillazine forum, http://forums.mozillazine.org/viewtopic.php?f=48&t=669795
CCing the extension maintainer (if I got his address right)
yeah, I think it's a component/uri registration issue, sorry about that, I'll try to fix soon.
Resolving as INVALID (NOTOURBUG) based on Comment 1 and Comment 2
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → INVALID
[Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9.1b2pre) Gecko/20081031 SeaMonkey/2.0a2pre] (home, optim default) (W2Ksp4) V.Invalid: WorksForMe.
Status: RESOLVED → VERIFIED
Target Milestone: --- → seamonkey2.0a2
Why set the target milestone to SeaMonkey2.0a2 ?
You need to log in before you can comment on or make changes to this bug.