88197 - File->Open web location doesnt work if composer window already exists

Status: VERIFIED DUPLICATE of bug 87910

(Core :: DOM: Editor, defect)

Description

[gary_Cope]

Build ID 2001062704 win 32

If an existing composer window is already open, then using the File->Open Web
Location dialog does nothing when chosing 'Open in new composer window'. This
does not work from either the navigator menu or the composer menu.

Steps to reproduce:

1. Open Composer from Tasks menu. A new Composer window is created.
2. In either Navigator window or Composer window choose File->Open Web Location
3. Enter url "www.mozilla.org" and choose "Open in: new Composer window"
4. Press ok.

What Happens:
Nothing.

What should Happen:
A new Composer window should be created with the chosen url available to be edited.

Comment 1

[rubydoo123]

odd, this works fine for me. Asking QA to verify

Comment 2

[Kathleen :Brade]

I'll look into this; I see the problem on my Mac mozilla trunk build.

Comment 3

[Chase Tingley]

Confirmed on Linux, 2001062721 trunk.

Comment 4

[rubydoo123]

ok, if you select to open a local file it works fine, if you select to open a
remote file it does not work.

Comment 5

[gary_Cope]

After filing this bug I came across bug 87910. That looks similar although it is
in reference to a different part of the UI (the 'File->Edit Page' menu item).

There is a patch in that bug which may fix this.

Comment 6

[Kathleen :Brade]

I have narrowed the problem down to the editorShell.checkOpenWindowForURLMatch 
call in utilityOverlay.js.

Wrapping that if with a try/catch gets this working again.
Next I'll investigate why checkOpenWindowForURLMatch is throwing us an error...

Comment 7

[Chase Tingley]

I suspect this may be another one from dougt's recent url checkins --
nsLocalFile* classes are now implementing GetURL and SetURL for themselves, and
those are definitely getting called by nsEditorShell::CheckOpenWindowForURLMatch().

Comment 8

[sujay]

IS this bug at all related to 71234 by any chance?

Comment 9

[Kathleen :Brade]

No, I don't think this is related to #71234.

cc dougt in case he knows what went wrong.

Comment 10

[Chase Tingley]

I just tried applying the patch for bug 87910 as suggested by [e-mail].

This appears to fix the problem.  I'm prepared to mark this a dup.

Comment 11

[Kathleen :Brade]

yes, I also think it's a duplicate; thanks for the pointer!


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

Comment 12

[sujay]

verified.