[e10s] New tab does not work on new window if parent is closed

NEW
Unassigned

Status

()

2 years ago
a year ago

People

(Reporter: g.medici, Unassigned)

Tracking

Trunk
Points:
---

Firefox Tracking Flags

(firefox49 affected, firefox50 affected, firefox51 affected, firefox52 wontfix)

Details

Attachments

(1 attachment, 1 obsolete attachment)

554 bytes, text/html
Details
(Reporter)

Description

2 years ago
User Agent: Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.143 Safari/537.36

Steps to reproduce:

Firefox 49.01 with e10s enabled.

Example Page:
<!DOCTYPE html>
<html>
  <head>
    <title>test.html</title>
	
    <meta name="keywords" content="keyword1,keyword2,keyword3">
    <meta name="description" content="this is my page">
    <meta name="content-type" content="text/html; charset=ISO-8859-1">
    
    <!--<link rel="stylesheet" type="text/css" href="./styles.css">-->

  </head>
  
  <body>
    <a  href="javascript:window.open('./test.html', '', 'height=400,width=400');">Open New Page</a><br>
    <a  href="./test.html" target="_blank">Open After</a><br>
  </body>
</html>

Open firefox point to this page.
Click on Open New Page. Close the parent window.
Click on Open After on the child window.

Disabling on about:config
browser.tabs.remote.autostart.2;false
Then all works the same as before.


Actual results:

The new tab was not created in the child window, and no new windows were created. Same thing happen with modal window.


Expected results:

A new tab should have been created or a new window with the new content. New modal window should be created too.

Updated

2 years ago
Component: Untriaged → Tabbed Browser

Updated

2 years ago
QA Whiteboard: [bugday-20161010]
I somewhat suspect this is a docshell issue, as that's what handles left-mouse clicks on links in content. right-clicking the link and clicking open in new tab/window/private-window still works.

Bill or Jim, how can we track this? I don't see tracking-e10s flags anymore. :-\
Status: UNCONFIRMED → NEW
status-firefox49: --- → affected
status-firefox50: --- → affected
status-firefox51: --- → affected
status-firefox52: --- → affected
Ever confirmed: true
Flags: needinfo?(wmccloskey)
Flags: needinfo?(jmathies)

Comment 2

2 years ago
(In reply to :Gijs Kruitbosch from comment #1)
> I somewhat suspect this is a docshell issue, as that's what handles
> left-mouse clicks on links in content. right-clicking the link and clicking
> open in new tab/window/private-window still works.
> 
> Bill or Jim, how can we track this? I don't see tracking-e10s flags anymore.
> :-\

Through normal status and tracking flags, the e10s specific flag has been retired since the e10s team is no longer meeting for triage.
Flags: needinfo?(jmathies)

Comment 3

2 years ago
Created attachment 8799448 [details]
test.html

Comment 4

2 years ago
Created attachment 8799450 [details]
test.html
Attachment #8799448 - Attachment is obsolete: true

Comment 5

2 years ago
(In reply to Jim Mathies [:jimm] from comment #4)
> Created attachment 8799450 [details]
> test.html

FWIW I'm not able to reproduce this bug using a local copy of test.html.
(Reporter)

Comment 6

2 years ago
(In reply to Jim Mathies [:jimm] from comment #5)
> (In reply to Jim Mathies [:jimm] from comment #4)
> > Created attachment 8799450 [details]
> > test.html
> 
> FWIW I'm not able to reproduce this bug using a local copy of test.html.

Bug still reproducible to me even with a local copy of test.html. 
Check that you have multiprocess windows enabled on about:support or add browser.tabs.remote.force-enable=true to about:config.
My setting also include "open new window in a new tab" checked.
(I was also able to reproduce on OS X with current nightly.)
Flags: needinfo?(wmccloskey)
Too late for firefox 52, mass-wontfix.
status-firefox52: affected → wontfix
You need to log in before you can comment on or make changes to this bug.