136599 - Microsoft Exchange webmail interface javascript popups broken when window.open is blocked

Status: VERIFIED DUPLICATE of bug 102481

(Tech Evangelism Graveyard :: English US, defect)

Description

[Mark Annand]

This involves Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.9+)
Gecko/20020409

MS exchange server 5.5's web-based interface relies on popups and these have
stopped working in the above build. Many other javascript popups are fine though.

Steps to reproduce:

1) Log into an MS exchange email account via a web browser (sorry, I'm unable to
 provide a link)

2) Select an email. It is displayed in a pop up window.

3) In the pop up, select eg the 'Reply to' icon.

What should happen: window changes to a 'reply to' window.

What happens: window vanishes, not replaced by anything, cursor hangs as 'Hour
glass' until it is moved.

Reproducible: every time.

Other info: I think builds up until 20020408 handled this and something broke
for the one in question.

Comment 1

[Boris Zbarsky [:bzbarsky]]

Please make sure you have everything enabled under Scripts & Windows preferences
and can still reproduce this bug.

Comment 2

[Mark Annand]

Thanks, it was as simple as that. With 'Preferences/Advanced/Scripts and
windows/Open unrequested windows' checked, the 'bug' vanishes. Uncheck the
preference, it returns, so Exchange's webmail's code here must be shaped in such
a way that a 'Reply to' window there is appearing to Mozilla as unrequested. (IE
simply works but offers no pop-up control, while Opera's pop-up window prefs
aren't as fine grained as Mozilla's and it provides the option to refuse/accept
everything)

Comment 3

[Boris Zbarsky [:bzbarsky]]

to tech evangelism.  I think there are other MS web apps that have a similar
problem...

Comment 4

[Jesse Ruderman]

Is Exchange Webmail the same as Outlook Web Access?  The description of this bug
sounds similar to bug 102481: with "unrequested windows" blocked, clicking reply
closes a window when Microsoft's programmers expect it to close a window and
open another one.

Comment 5

[Mark Annand]

Yes, I think 136599 is a duplicate of 102481 ... sorree! (I searched and
searched too ...)

Thanks

Mark

Comment 6

[Boris Zbarsky [:bzbarsky]]

Mark, thanks for the response!

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

Comment 7

[Kai Lahmann (is there, where MNG is)]

v