28683 - Opening a remote location via Open Location doesn't work if loading into Composer

Status: VERIFIED FIXED

(Core :: DOM: Editor, defect, P3)

Description

[Charles Manske]

From either a brower or composer window:
Use the menu command File | Open Web Location to bring up a dialog to load
remote pages. Enter a valid http: URL (e.g.: 
http://blues/users/bijals/publish/composer/composerbor2.htm)
and you get an error message.
Note that if window with file already exists, it does switch to that window.
Or if the URL is first loaded in a browser window, and File | Edit Page is 
used, it loads correctly.
We are using the exact same code as the browser to call the Open Web Location
dialog, by the way.
Simon: Feel free to investigate this if you have time!
Does anyone feel this is a beta1 issue? I bet the fix is simple.

Comment 1

[Kathleen :Brade]

I've seen this on Mac today as well; this is a regression from last week.

Comment 2

[Kathleen :Brade]

add keyword beta1
Charley--any ideas what caused this regression?

Comment 3

[Charles Manske]

No. Will investigate more thoroughly if judged to be PDT+

Comment 4

[leger]

Putting on PDT+ radar for beta1.

Comment 5

[Charles Manske]

Checked in 2/23

Comment 6

[bijals (gone)]

In 2/23/00-08 early morning builds, I still get an error dialog.  However, I can 
cut/paste now.

Comment 7

[sujay]

still a problem in 2/24 build....

I try loading any URL on the net into the composer via Open Web Location
and it doesn't work..I get an error panel

in browser it works..

Comment 8

[Charles Manske]

I thought I was going crazy -- it worked when I tested it.
What is happening now is that loading a URL via this dialog works into either 
a Browser and Composer works, but only if the starting window is a Browser.
If you are in a Composer window and use "Open Location", it FAILS to load
into either a Browser or Composer.
So this is really a different issue than the one originally fixed.
I bet it's a "permission to load window is refused" issue.

Comment 9

[Charles Manske]

Ok, I have a very simple fix now (it was tough to diagnose!)
Simple set a checkbox value to "false" when loading from editor -- this 
checkbox was being hidden, but the initialized checked state was "true",
which made it act like we were loading from a non-existing browser window,
thus the JS exception.

Comment 10

[Simon Fraser [no longer active]]

cc michael lowe, who wrote that dialog

Comment 11

[Charles Manske]

Attachment: Diff for bug fix

Comment 12

[Joe Francis]

i've tested charlie's fix on the mac - works fine.

Comment 13

[Charles Manske]

Checked in late 2/24

Comment 14

[sujay]

verified in 2/25 build.