77864 - crash when plug in requiring page is opened while Composer is open.

Status: VERIFIED WORKSFORME

(Core Graveyard :: Plug-ins, defect, P3)

Description

[hirata masakazu]

2001042608 Mtrunk for Mac.
No plugins other than installed by default.
Open browser.
Goto URL. This is actually a left frame of the entire page.
Command+E to open Composer.
Switch window back to Browser.
Click the link above MAIL image at the bottom, which has a link;
http://www.geocities.co.jp/CollegeLife-Labo/9292/indexb.htm
Result:Crash.

Comment 1

[hirata masakazu]

Attachment: stack trace of the crash while opening a page that requires plugin

Comment 2

[Peter Lubczynski]

Looks like we are trying to instantiate the plugin in Composer. How can one tell 
composer is creating frames? Is there something I can QI on in the PresContext?

Comment 3

[Charles Manske]

Simon or Mike know how to find out if there's an editor from
webshell or prescontext.

Comment 4

[Simon Fraser [no longer active]]

You currently can't (easily) tell if the page is being opened in composer.
Can Composer do something to disable plugins in its content area? That's probably 
the right thing to do.

Comment 5

[Peter Lubczynski]

I think that's what this bug is about.

I'm not quite sure how composer works i.r.t content and frames but if a seperate 
content tree is created, perhaps the object tag could be replaced with another 
placeholder.

Comment 6

[Peter Lubczynski]

I just noticed that the DocShell has a protect member variable mAllowPlugins 
which would sounds like something to key off of. Can composer trip that flag in 
the Docshell?

Does this happen on all platforms? Crashers are P2 at least. Stealing away.

Comment 7

[Peter Lubczynski]

The testcase does not crash for me. Other pages with flash or other plugins WFM
in trunk 0607 on Win32 and Mac.

Please re-open if this still happens for you with an updated build or other
testcase.

Comment 8

[shrirang khanzode]

verif orking on win mac trunk 0621