Closed Bug 162159 Opened 22 years ago Closed 20 years ago

window.open works only once in Outlook Web Access

Categories

(Core :: DOM: Core & HTML, defect)

Product:
Core
Component:
DOM: Core & HTML
Platform:
PowerPC
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED INVALID

People

(Reporter: seres, Unassigned)

References

Details

(Keywords: qawanted) 

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:1.1b) Gecko/20020722
BuildID:    2002072203

Outlook Web Access opens each message on a new window using a javascript that
calls window.open. Everything works fine when the script is called the first
time (a message name is clicked to view the message) but after this window is
closed, no new windows will show up. Reloading the page does not help.

Reproducible: Always
Steps to Reproduce:
1. Log in to Outlook Web Access
2. Click a message in Inbox. A new window appears. Everything ok so far.
3. Close the message window
4. Click a message again.

Actual Results:  Result: No new message will appear. No error messages, nothing.

Expected Results:  A new message window should appear.

A html code snippet from inbox:
<a
HREF='JavaScript:parent.openNewWindow("/exchange/forms/IPM/NOTE/frmRoot.asp?index=8&obj=00000000D30104128B1FD511BCF70008C7243B7C0700816025DE27A0D311BCE30008C7243B7C000000BAA5630000816025DE27A0D311BCE30008C7243B7C0000011D89580000&command=open",
"00000000D30104128B1FD511BCF70008C7243B7C0700816025DE27A0D311BCE30008C7243B7C000000BAA5630000816025DE27A0D311BCE30008C7243B7C0000011D89580000",
640, 500)'>

JavaScript code (hopefully without typos):

file main_fr.asp:
<script language="Javascript">

function openNewWindow(fileName,windowName,theWidth,theHeight) {
  if (windowName == "newMessageWindow")
  {
    // generate random window ID
    windowName = new String(Math.round(Math.random() * 100000));
  }
 
window.open(fileName,windowName,"toolbar=0,location=0,directories=0,status=1,menubar=1,scrollbars=1,resizable=1,width="+theWidth+",height="+theHeight)
}
</script>
do you have "unrequested windows" turned off?
I also have Outlook Web Access at work but can't reproduce the issue as clicking
on an e-mail opens the message in current window/frame, it doesn't use window.open
Cristian, before you try this again, do Tools/Web Development/JavaScript Console. Click the 
"Clear" button. Then, try reproducing this problem again, and let us know if any errors, warning, 
etc. are displayed on that console.
"unrequested windows" is turned on at the moment. If it is turned off, Outlook
can not open no message windows at all.

I do not know exactly what I did, but immediately after I sent this bug report,
web mail worked perfectly for a moment. Then I played with the "unrequested
windows" option and now I am in the same situation as before: new window opens
once, but only once.

There are no messages at all in JavaScript console. Is there something I could
do with JavaScript Debugger to help you?
Some additional info on a perhaps related problem that I have using Outlook Web
Access with Unrequested Windows turned ON.

Entering and reading: no problemo
Replying or forwarding: nothing at all happens

I am not very savvy about the inner workings and meaning of the term unrequested
window, but it would seem to me that I did request this window, a script that
was triggered by my input wanted to open it.

Turning Unrequested Windows OFF makes everything work just fine.

Adding qawanted. Someone with OWA access somewhere needs to triage this.
Keywords: qawanted
There's a real issue here, but I don't know exactly what it is.  Accessing
"Microsoft Outlook Web Access for Microsoft Exchange Server" Version 5.5 SP4
with Linux builds from MOZILLA_1_0_BRANCH circa 20020711 up to
MOZILLA_1_1_BRANCH circa 20020911, I can confirm that:

1.  With "Allow Scripts to...Open Unrequested Windows" turned *off*, opening
multiple messages (in multiple windows) works fine but trying to reply or
forward merely closes the message window.

2.  With "Allow Scripts to...Open Unrequested Windows" turned *on*, everything
works as expected.  You can open multiple messages, and replying or forwarding
closes the message window and opens a new message composition window.

However, that's *today*.  I'm quite sure that my experience in the past has been
different.  When I accessed it from a friend's Windows Netscape 7.0 a couple
weeks ago, I'm positive that forwarding didn't work whether "Open Unrequested
Windows" was checked or not.  I'm also quite sure that I looked at this problem
before with some Linux Mozilla builds and verified that "Open Unrequested
Windows" had no effect *AND* that there were no messages in the JavaScript
console to reveal the problem.

I can't say if the change is because of a server-side upgrade, Mozilla
differences from architecture to architecture, changes in the Mozilla codebase,
an intermittent bug that I haven't managed to trigger in my tests today, or some
combination of the above.

Cristian, what version of Microsoft Outlook Web Access are you accessing?  Can
you reproduce the problem with a newer Mozilla build?  Also, this is almost
surely a dead end, but can you verify that typing the URL:

javascript:window.open("", new String(Math.round(Math.random()*100000)))

into the location bar of a window correctly opens a new (empty) window?  And
that clicking on that URL and hitting enter on it a few times opens more
windows?  Maybe it's some freakish, architecture-dependent problem with opening
windows with random numbers for names.
I do not know the version of Outlook Web Access. I guess there are not any other
way to check it than contact the administrator of the site?

This is interesting: javascript:window.open("", new
String(Math.round(Math.random()*100000))) typed into the location bar does NOT
open a new window, but a text "null" in current window. I checked the same
string in IE 5.1:mac and it opened a new window.

I am currently using build 20020826. I am having the same problem than before.
Sorry for the long delay.

What if you just type:

javascript:window.open("","12345")

into the location bar?  On my Linux Mozilla, I get a new window opened.  Does
that work on your Mac?

If it does, what does:

javascript:Math.round(Math.random()*100000)

give you?  (It gives me a random 5 digit number in the main browser display
area.)  How about this?

javascript:new String(Math.round(Math.random()*100000))

(For me, it does the same thing: it gives a random 5 digit number.)

javascript:window.open("","12345") does not open a new window - the contents of
the current window is replaced by a text 'null', no new window is opened.

javascript:Math.round(Math.random()*100000) and
javascript:new String(Math.round(Math.random()*100000))

generated random numbers normally.

Javascript window.open works flawlessly in many situations, for example 'New
window!" button at http://www.pageresource.com/jscript/jwinopen.htm works fine.
Okay.  Is it barfing on the numeric window name or the blank URL?  Which of
these works:

javascript:window.open("","abcde")
javascript:window.open("http://www.mozilla.org","12345")

Neither of those javascripts work. Perhaps window.open does not work if typed to
the location bar in OS X for some reason?

I wrote a minimal html test page:
<html><head><title>Test</title>
<script type="text/javascript">
<!--
F1 = window.open("http://www.mozilla.org/","win1");
//-->
</script>
</head><body>
</body></html>

Window.open works fine here.
Does your HTML test page work with any or all of the following?

F1 = window.open("", new String(Math.round(Math.random()*100000)));
F1 = window.open("","12345");
F1 = window.open("","abcde");
F1 = window.open("http://www.mozilla.org/","12345");

If it works with the first, the dead end I talked about earlier really is a dead
end, though it's a mystery why "javascript:window.open(...)" doesn't work in the
location bar on OS X.

F1 = window.open("", new String(Math.round(Math.random()*100000)));
opened a new window. Dead end as you said.
On my PC running Windows 98SE (4.10.2222), using Mozilla 1.1 build 20020826, I
consistently reproduce the behavior described in Additional Comment #7 From
Kevin Buhr  2002-09-14 12:35, i.e. with allow scripts to open unrequested
windows unchecked in prefs, clicking a reply button [Javascript:
DoCommand('reply')] in an open message window in "Microsoft Outlook Web Access
for Microsoft Exchange Server," Version 5.5 SP4, causes the message window to
close and does not open a window with a reply form.  The same result occurs if
the forward or replyall commands are attempted.  All work normally with
unrequested windows checked in prefs.  I have checked with our system
administrator, who indicates that there have been no upgrades to our MS Exchange
Server software for the last several months.
If there is other information that anyone would like to coach me to extract (I
am an html and javascript ignoramus), I would be pleased to assist in that way.
 Should this (i.e. Buhr's comment #7) be entered as a separate bug, as it does
not match exactly the problem first described by the writer of this bug?
*** Bug 176152 has been marked as a duplicate of this bug. ***
Note, the duplicate bug 176152 was also reported on MacOS X,
as this one was. Confirming bug based on two separate reports -
Status: UNCONFIRMED → NEW
Ever confirmed: true
*** Bug 189959 has been marked as a duplicate of this bug. ***
Mass-reassigning bugs to dom_bugs@netscape.com
Assignee: jst → dom_bugs
Anyone out there that can possibly work on this 2 year old bug?  The problem
still exists, even with Firefox 0.9.2, brand new profile, no extensions
installed.  As mentioned in the previous comments, disabling the "Block Popup
Windows" feature allows the javascript calls to work properly.  Enabling allows
a message to open in a separate window, but prevents
javascript:DoCommand('reply'), etc. from working and actually closes the open
message window.  No error msgs or warnings appear in the JS Console.
Anyone out there that can possibly work on this 2 year old bug?  The problem
still exists, even with Firefox 0.9.2, brand new profile, no extensions
installed.  As mentioned in the previous comments, disabling the "Block Popup
Windows" feature allows the javascript calls to work properly.  Enabling allows
a message to open in a separate window, but prevents
javascript:DoCommand('reply'), etc. from working and actually closes the open
message window.  No error msgs or warnings appear in the JS Console.
The point is that this application IS using unrequested popups.  And we block
those.  Sounds like everything works as expected to me.  If you need popups to
work for this one site, that's what white-listing is for.
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → INVALID
So if I click on a menu icon which invokes a JS command in the same window, same
application, this is opening an unrequested pop-up??  I disagree.  What makes it
unrequested?  And if it were an unrequested window, why does no pop-up warning
icon appear in the lower left corner of my screen?

The problem here is that with or without pop-up blocking enabled, I can open an
email message in a new window.  It is once I am in the new window that I cannot
activate additional commands if pop-up blocking is enabled.  If I disable it,
everything works as it should.  If I add the site to the white-list, everything
works as it should.

White-listing the site as a work around resolves the issue, but isn't there
still a problem here?
> So if I click on a menu icon which invokes a JS command in the same window,
> same application, this is opening an unrequested pop-up??

Of you click an icon that does two different things -- set a timer to open a
popup window and go to a different page -- is that an unrequested pop-up? 
That's the situation here,  as near as I can tell.  The window is being opened
in a way that makes it indistinguishable from malicious popups.

> why does no pop-up warning icon appear in the lower left corner of my screen?

That sounds like a bug in the UI (firefox-specific, I assume, since in SeaMonkey
that icon is on the right, not on the left).
You need to log in before you can comment on or make changes to this bug.