90925 - Editor's Browse button brings up the Home Page

Status: VERIFIED DUPLICATE of bug 59497

(Core :: DOM: Editor, defect)

Description

[Katsuhiko Momoi]

** Observed with 7/15/2001 Win32 Branch build **

Hopefully there is already a bug filed for this.

1. Create a new HTML document. At some point in the editing process,
   press the Browse button.
2. This should open a new Browser window if one is not open and
   show the edited page in the Browser. Instead, it opens to
   the Home Page specified in the Navigator prefrences.

I think this is a bad bug and needs to be fixed.

Comment 1

[Katsuhiko Momoi]

I frogot to mention one condition. There should be a browser page open
already for this problem to occur. It does not matter whether the
page opened is this Editor page in the Browser or some other page.
In either case, the action opens the Home Page.

Comment 2

[Boris Zbarsky [:bzbarsky]]

Looks like bug 89691

Comment 3

[rubydoo123]

opened composer
browse button is disabled
entered text (browse button enabled)
selected browse 
prompt to save document
browser opened, and document rendered

this works for me using branch build from 7/15/01

if the problem occurs on second selection of the browse button -- that would be 
59497

Comment 4

[sujay]

marking verified. Momoi, please reopen if you disagree...

Comment 5

[Katsuhiko Momoi]

Re-opening this bug because it still occurs with
7/21/2001 Win32 branch build.

Comment 6

[Katsuhiko Momoi]

I am going to attach a composer file that I used to
reproduce this problem.

Comment 7

[Katsuhiko Momoi]

Attachment: A small HTML file.

Comment 8

[Katsuhiko Momoi]

Here are the steps I followed to reproduce this problem.

0. Have the Navigator Home Page set to:

http://home.netscape.com/ja

1. Open the test file attached in the Composer window.
2. Add a character or two and save it.
3. Now click on the "Browse" button.
4. This will either open the Navigator Home Page or
   the intended page. If it is the latter, then 
   leave that page alone and go to step 5.
5. (If it fails to reproduce this problem), then
   click on the Browse button again. This is usually
   when I see this problem, i.e. every time I save the
   document and try to see it in a Browser window.

CC'ing a bunch of people because there are still a few other bugs
in which the Navigator Home Page is opened instead of the
real intended page.

Comment 9

[selmer (gone)]

Bhuvan, is this bug fixed by 91585 or Jag's fix?

Comment 10

[racham]

Jag's fix may have done some good for the first problem reported here. Clicking
on the browse button always brings the page in edit in the browser window. But
the second part where user clicks on Browse button again, the window opened for
this purposes shows up with no content.

When clicked on browse button following the steps given by momoi, here are the
observations :

Case 1: 
First time clicked on browse button : Browser window gets opened with intended
page (i.e., one just edited)

Case 2:
Clicking on Browse on subsequent occasions : I get the browser window opened in
case 1 and it is just blank.

Case 3:Close the browser window opened (which originally came up when clicked on
browse button) and click on browse button again. It does load the intended (the
page in editing) page. However, clicking browse again falls under Case 2.

From one of the updates in this bug, looks like there is already a bug about the
 weird state that occurs when browse button is clicked multiple times (bug 50497).

But we need to know why do we load blank page all the time, when clicked on
browse button second or any subsequent times. Jag, is there an explaination for
this? It looks like the second time when the browse button is clicked, the
window opens to do the right seemed to be not getting the URL to display....??

Above observations are with branch debug build (with jag's patch from 65993 +
morse's patch backed out for bug 91585).

Comment 11

[racham]

I typed 'bug 50497' instead of 'bug 59497' in my last update. Please replace the
bug number correctly with bug 59497 for your reference. This is about the
problem that happens when browse button is clicked multiple times.

Comment 12

[jag (Peter Annema)]

Actually, this is a completely different bug.

When window.openDialog(url, name, options, arg1, arg2, ...) is called with a
non-null name, all calls to an open window with that name don't pass on arg1,
arg2, etc. Put differently, the first time it will work fine, consecutive times
it will fail. Until you close the window, then the first window open will work,
consecutive calls will fail again.

It seems to be a Window Watcher problem, let me look at this. cc'ing danm,
attaching testcase.

Comment 13

[jag (Peter Annema)]

Attachment: [testcase] pressing button opens named window with parameter.

Comment 14

[jag (Peter Annema)]

Serves me right for posting that comment even though bugzilla warned me there
were changes in between :-) I think you're right, this is bug 59497 (even though
that bug seems to have morphed a bit).

Comment 15

[Katsuhiko Momoi]

I don't mind if this is a duplicate of another bug. 
What I do mind is that there seems to be no activity
for that bug for 3 weeks. If we can get moving on
fixing the problem, that would be great.

Comment 16

[sujay]

Beth, can you check if this is a DUP of 89691 ?

Comment 17

[sujay]

cc: kin

Comment 18

[sujay]

Kat, left you a message. Can you check to see if this bug is a DUP
of the morphed bug 59497 ? 

Comment 19

[rubydoo123]

yes, this seems to be a dup of 59497

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

Comment 20

[sujay]

verified. Kat, reopen if you disagree.