91477 - Security manager blocking javascript: URL, possibly incorrect

Status: VERIFIED DUPLICATE of bug 92061

(Core :: Security: CAPS, defect, P2)

Description

[Jeet Shahani]

In Mozilla 0.6 and Netscape 6.01,  it brings up a pop up window from a
javascript call listed below.
I have attached the screen shot in a message(dated July 19th 2001) in the
newsgroup mozilla.java.  Please see screen shot for further information.
I have attached the javascript error below.

I get the following error in WebClient when I try to click ont he following
link from WebClient.

1)Go to the following url, and
http://www.yahoo.com/r/rmf

2)Click on the first <trailer> link and you will get the following error listed
at the end of the message.

java.beans.PropertyChangeEvent[source=org.mozilla.webclient.test.MyEMJF[frame0,0
,0,812x622,invalid,layout=java.awt.BorderLayout,resizable,title=EmbeddedMozila#1
,defaultCloseOperation=HIDE_ON_CLOSE,rootPane=javax.swing.JRootPane[,4,42,804x57
6,invalid,layout=javax.swing.JRootPane$RootLayout,alignmentX=null,alignmentY=nul
l,border=,flags=3586,maximumSize=,minimumSize=,preferredSize=],rootPaneCheckingE
nabled=true]]

debug: edburns: EMJF Currently Viewing: javascript:clickHandler('http://rd.yahoo
..com/movies/trailers/1804857429/?http://mediaframe.yahoo.com/launch?lid=wmv-56-p
..919377,wmv-100-p.919378,wmv-300-p.919379&p=movies&.spid=1804857429&.dist=MGM');

JavaScript error:
line 0: uncaught exception: [Exception... "Failure"  code: "-2147467259" nsresu
lt: "0x80004005 (NS_ERROR_FAILURE)"  location: "http://movies.yahoo.com/ Line: 7
"]

Comment 1

[Jeet Shahani]

Attachment: Screen Shot of process through Mozilla and Netscape

Comment 2

[Jeet Shahani]

Also noticed the same failure code on another site.  This maybe useful
information too.

debug: edburns: Currently Viewing: http://www.indiafm.com/
JavaScript error:
 line 0: uncaught exception: [Exception... "Failure"  code: "-2147467259" nsresu
lt: "0x80004005 (NS_ERROR_FAILURE)"  location: "http://servedby.advertising.com/
pops=1/site=58685/bnum=42021184 Line: 1"]

debug: edburns: Currently Viewing: http://ad3.adcept.net/cgi-bin/adceptdelivery.
cgi?random_key=19/6/10111:1:200.21105383604614764&banner_height=60&banner_width=
468&keywords=none;www.indiafm.com;entertainment;music;movies;home;indiafm-home;&
host_name=www.indiafm.com&adtype=HTML&url_name=www.indiafm.com/
JavaScript error:
 line 0: uncaught exception: [Exception... "Failure"  code: "-2147467259" nsresu
lt: "0x80004005 (NS_ERROR_FAILURE)"  location: "<unknown>"]

Comment 3

[Jacob Kjome]

Using build 2001071903 on Win2k (SP2), I am crashing on the site that was 
provided by the Reporter in his last comment:  http://www.indiafm.com/

I think this may be related to the bug I just reported:  bug 91479

Might be able to dup that one.

Talkback ID#: TB33090390X

Note:  I included a talkback id in bug 91479.  That one was:  TB33088717Q

Jake

Comment 4

[Asa Dotzler [:asa]]

Incident ID 33090390
Stack Signature CopyChars1To2 f71e171e
Bug ID
Trigger Time 2001-07-19 08:32:18
User Comments Went to this URL after seeing it mentioned in bug 91477. This also
seems like the behavior that I reported in bug 91479. I put a talkback ID in
that bug. The stack trace might be the same as in this one. We'll see.. Jake
Build ID 2001071905
Product ID MozillaTrunk
Platform ID Win32
Stack Trace
CopyChars1To2 [d:\builds\seamonkey\mozilla\string\obsolete\bufferRoutines.h,
line 278]
nsStr::StrAppend [d:\builds\seamonkey\mozilla\string\obsolete\nsStr.cpp, line 185]
nsStr::StrAssign [d:\builds\seamonkey\mozilla\string\obsolete\nsStr.cpp, line 160]
nsString::nsString [d:\builds\seamonkey\mozilla\string\obsolete\nsString2.cpp,
line 101]
nsFont::nsFont [d:\builds\seamonkey\mozilla\gfx\src\nsFont.cpp, line 51]
nsStyleFont::nsStyleFont
[d:\builds\seamonkey\mozilla\content\shared\src\nsStyleStruct.cpp, line 192]
nsStr::Alloc [d:\builds\seamonkey\mozilla\string\obsolete\nsStr.cpp, line 683]
nsStr::Realloc [d:\builds\seamonkey\mozilla\string\obsolete\nsStr.cpp, line 709]
nsRuleNode::WalkRuleTree
[d:\builds\seamonkey\mozilla\content\html\style\src\nsRuleNode.cpp, line 940]
nsRuleNode::GetFontData
[d:\builds\seamonkey\mozilla\content\html\style\src\nsRuleNode.cpp, line 661]
nsRuleNode::GetStyleData
[d:\builds\seamonkey\mozilla\content\html\style\src\nsRuleNode.cpp, line 4522]
nsStyleContext::GetStyleData
[d:\builds\seamonkey\mozilla\content\base\src\nsStyleContext.cpp, line 394]
nsStyleContext::CalcStyleDifference
[d:\builds\seamonkey\mozilla\content\base\src\nsStyleContext.cpp, line 599]
CaptureChange
[d:\builds\seamonkey\mozilla\layout\html\base\src\nsFrameManager.cpp, line 1598]
FrameManager::ReResolveStyleContext
[d:\builds\seamonkey\mozilla\layout\html\base\src\nsFrameManager.cpp, line 1688]
FrameManager::ReResolveStyleContext
[d:\builds\seamonkey\mozilla\layout\html\base\src\nsFrameManager.cpp, line 1834]
FrameManager::ReResolveStyleContext
[d:\builds\seamonkey\mozilla\layout\html\base\src\nsFrameManager.cpp, line 1834]
FrameManager::ReResolveStyleContext
[d:\builds\seamonkey\mozilla\layout\html\base\src\nsFrameManager.cpp, line 1834]
FrameManager::ReResolveStyleContext
[d:\builds\seamonkey\mozilla\layout\html\base\src\nsFrameManager.cpp, line 1834]
FrameManager::ReResolveStyleContext
[d:\builds\seamonkey\mozilla\layout\html\base\src\nsFrameManager.cpp, line 1834]
FrameManager::ReResolveStyleContext
[d:\builds\seamonkey\mozilla\layout\html\base\src\nsFrameManager.cpp, line 1834]
FrameManager::ComputeStyleChangeFor
[d:\builds\seamonkey\mozilla\layout\html\base\src\nsFrameManager.cpp, line 2078]
nsCSSFrameConstructor::AttributeChanged
[d:\builds\seamonkey\mozilla\layout\html\style\src\nsCSSFrameConstructor.cpp,
line 10050]
StyleSetImpl::AttributeChanged
[d:\builds\seamonkey\mozilla\content\base\src\nsStyleSet.cpp, line 1156]
PresShell::AttributeChanged
[d:\builds\seamonkey\mozilla\layout\html\base\src\nsPresShell.cpp, line 4937]
nsXULDocument::AttributeChanged
[d:\builds\seamonkey\mozilla\content\xul\document\src\nsXULDocument.cpp, line 1615]
nsXULElement::SetAttribute
[d:\builds\seamonkey\mozilla\content\xul\content\src\nsXULElement.cpp, line 3046]
nsXULElement::SetAttribute
[d:\builds\seamonkey\mozilla\content\xul\content\src\nsXULElement.cpp, line 1396]
nsContentTreeOwner::ApplyChromeFlags
[d:\builds\seamonkey\mozilla\xpfe\appshell\src\nsContentTreeOwner.cpp, line 621]
nsXULWindow::OnChromeLoaded
[d:\builds\seamonkey\mozilla\xpfe\appshell\src\nsXULWindow.cpp, line 716]
nsWebShellWindow::OnStateChange
[d:\builds\seamonkey\mozilla\xpfe\appshell\src\nsWebShellWindow.cpp, line 1286]
nsDocLoaderImpl::FireOnStateChange
[d:\builds\seamonkey\mozilla\uriloader\base\nsDocLoader.cpp, line 1095]
nsDocLoaderImpl::doStopDocumentLoad
[d:\builds\seamonkey\mozilla\uriloader\base\nsDocLoader.cpp, line 735]
nsDocLoaderImpl::DocLoaderIsEmpty
[d:\builds\seamonkey\mozilla\uriloader\base\nsDocLoader.cpp, line 632]
nsDocLoaderImpl::DocLoaderIsEmpty
[d:\builds\seamonkey\mozilla\uriloader\base\nsDocLoader.cpp, line 635]
nsDocLoaderImpl::OnStopRequest
[d:\builds\seamonkey\mozilla\uriloader\base\nsDocLoader.cpp, line 563]
nsLoadGroup::RemoveRequest
[d:\builds\seamonkey\mozilla\netwerk\base\src\nsLoadGroup.cpp, line 517]
nsStreamIOChannel::OnStopRequest
[d:\builds\seamonkey\mozilla\netwerk\base\src\nsInputStreamChannel.cpp, line 465]
nsOnStopRequestEvent::HandleEvent
[d:\builds\seamonkey\mozilla\netwerk\base\src\nsRequestObserverProxy.cpp, line 161]
PL_HandleEvent [d:\builds\seamonkey\mozilla\xpcom\threads\plevent.c, line 591]
PL_ProcessPendingEvents [d:\builds\seamonkey\mozilla\xpcom\threads\plevent.c,
line 524]
_md_EventReceiverProc [d:\builds\seamonkey\mozilla\xpcom\threads\plevent.c, line
1072] 

I'm seeing this too. I got almost identical stack but I was in mailnews.

Comment 5

[Jacob Kjome]

Now that bug 91479 is fixed (fix for bug 90081 was backed out), I am able to
load the site ( http://www.indiafm.com/ ) that I was crashing on before.

However, I don't see the failure code.  I see a warning in the Javascript Console:

"Attempt to load a javascript: URL from one host
in a window displaying content from another host
was blocked by the security manager."

Maybe this can be marked as a dup of bug 91479 now?

jake

Comment 6

[basic]

hoju: no, the warning you see is the same as the Javascript "failure"

Comment 7

[basic]

Sending to security to see if this bug is valid

Comment 8

[Mitchell Stoltz (not reading bugmail)]

I'm fairly sure this is a dup of 92061, but I will check again after I've fixed
that one.

Comment 9

[basic]

marking depend per mstoltz's comment

Comment 10

[Mitchell Stoltz (not reading bugmail)]

Confirmed as a dup. Fix should go in today if I get approval.

*** This bug has been marked as a duplicate of 92061 ***

Comment 11

[bsharma]

Verified on 2001-10-10-branch build on WinNt

The above url is lading without any warning in the JS console.