Closed Bug 1206885 Opened 9 years ago Closed 8 years ago

[e10s] Firefox x64 doesn't open some Popup-Windows

Categories

(Core :: Widget: Win32, defect)

42 Branch
x86_64
Windows 7
defect
Not set
normal

Tracking

()

RESOLVED WONTFIX
Tracking Status
e10s + ---

People

(Reporter: Kokujou, Assigned: mconley)

References

Details

(Keywords: 64bit)

Attachments

(1 file)

Attached image Unbenannt.JPG
User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:42.0) Gecko/20100101 Firefox/42.0
Build ID: 20150920004018

Steps to reproduce:

i did visit the site: http://mail.inf.hs-anhalt.de
(maybe it occurs with all websites of the Outlock Web App kinds)
I create a new message and clicked the button for appending a attachment.


Actual results:

Nothing


Expected results:

It should open a new window (not tab, even if its setted up to open tab instead of window), which manages the attachment uploading.
Keywords: 64bit
OS: Unspecified → Windows 7
Hardware: Unspecified → x86_64
The problem does not happen in x32 Version. I tested it with the x32 Version and the same addons installed, as well as the same settings like popup-blocker.
Also there is no notification about popup blocking.
I have tested this issue on latest Nightly (45.0a1) build and I was able to reproduce it. And also on latest Aurora build (44.0a2).

However I could not reproduce this on latest Firefox release 42.0 how Kokujou reported, but judging from attached screenshot, he was testing this in an Aurora build also.

Here are the user agents for the tested builds:

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:42.0) Gecko/20100101 Firefox/42.0
Build ID:   20151029151421

User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:45.0) Gecko/20100101 Firefox/45.0
Build ID: 20151117030242

User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:44.0) Gecko/20100101 Firefox/44.0
Build ID: 20151117004023
Status: UNCONFIRMED → NEW
Component: Untriaged → DOM
Ever confirmed: true
Product: Firefox → Core
Can you reproduce on nightly with e10s disabled?
Flags: needinfo?(paul.pasca)
(In reply to Boris Zbarsky [:bz] from comment #3)
> Can you reproduce on nightly with e10s disabled?

The bug only reproduces if e10s is enabled. With e10s disabled, the file attachment window correctly appears.
Flags: needinfo?(paul.pasca)
Blocks: e10s
tracking-e10s: --- → ?
Component: DOM → Widget: Win32
Summary: Firefox x64 doesn't open some Popup-Windows → [e10s] Firefox x64 doesn't open some Popup-Windows
Kokujou, we're unclear what dialog is failing to appear.  Can you post a screenshot of the expected dialog(attachment manager)? Thanks.
Flags: needinfo?(Kokujou)
Ah, it's an add attachment dialog window of some sort.  Does anyone have an Microsoft/Outlook account?
Flags: needinfo?(Kokujou)
Flags: needinfo?(blassey.bugs)
I can reproduce this. I get the outline of the popup window and then it disappears. In the console I get:

Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience. For more help http://xhr.spec.whatwg.org/ uglobal.js:1:29180
This site makes use of a SHA-1 Certificate; it's recommended you use certificates with signature algorithms that use hash functions stronger than SHA-1.[Learn More]
Flags: needinfo?(blassey.bugs)
Assignee: nobody → mconley
the features being passed in the openWindow call are "-moz-internal-modal=1,status=1,width=450px,height=285px,scrollbars=0,centerscreen=1,scrollbars=1,centerscreen=1,resizable=0"

Mike, any of these features raise any flags for you?
Flags: needinfo?(mconley)
> -moz-internal-modal=1

This is used for showModalDialog. We don't support showModalDialog in e10s. OWA will not work with Edge and Chrome either.
emk is right - looking at the nsWindowWatcher and nsGlobalWindow code, the only way that -moz-internal-modal would ever have been paid attention to is if it was called from showModalDialog.

According to this article[1], Edge and Chrome are already broken here.

And reading [2] (and from what I recall from meetings), we don't plan to support showModalDialog for 46 with e10s.

So this sounds like a WONTFIX to me. Sound good, blassey?


[1]: http://www.infoq.com/news/2014/09/chrome-showmodaldialog
[2]: https://www.fxsitecompat.com/en-US/docs/2015/window-showmodaldialog-will-be-removed/
Flags: needinfo?(mconley) → needinfo?(blassey.bugs)
Mike, sounds like this should move over to your world. We're deprecating showModalDialog, and that seems to break Outlook Web Access.
Flags: needinfo?(blassey.bugs) → needinfo?(miket)
I see a number of people with this same issue in Chrome... :/

https://code.google.com/p/chromium/issues/detail?id=421867
https://code.google.com/p/chromium/issues/detail?id=410283 (comment #78 suggests that shimming window.showOpenModalDialog to window.open possibly fixes the issue?)

https://code.google.com/p/chromium/issues/detail?id=408203#c20 suggests that the issue is only OWA 2010 (and older?)... if this one of those enterprise things that never receives updates, we might be in trouble here.
Flags: needinfo?(miket)
I commented on the PR to remove showModalDialog: https://github.com/whatwg/html/pull/374#issuecomment-171466693
Pretty sure this is something we were going to get rid of regardless of shipping e10s. Re-nomming for triage discussion, but I'm pretty sure this is a minus.
If we're going to remove it we need to understand we're going to break attachments in OWA 2010 like Chrome and Edge have. 

I'm skeptical evangelism is worth our time here -- upgrading to a current OWA setup is a way more expensive proposition than asking users to use IE or Safari. I would probably recommend we WONTFIX this bug (and similar ones). :/
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: