874701 - No panels with browser.tabs.remote=true

Status: VERIFIED WORKSFORME

(Core :: Graphics: Layers, defect)

Description

[Mark Hammond [:markh] [:mhammond] [PTO until Sept 7]]

If I set browser.tabs.remote=true, then many panels and popups fail to work.  Eg, clicking on the "downloads" button fails to display a panel, and the HTML5 form validation popup also fails to appear.  Note that my experiments show that the panels *think* they are working correctly (eg, popup events are all sent, tests still pass etc) - but they can't be seen.  This works fine on Linux.

Comment 1

[Mark Hammond [:markh] [:mhammond] [PTO until Sept 7]]

Graphics section of about:support - but note this is taken from a profile without browser.tabs.remote set to true - most about: pages also fail for me once that pref is set:

        Adapter Description
        NVIDIA GeForce 8400 GS

        Adapter Description (GPU #2)
        Intel(R) HD Graphics 4000

        Adapter Drivers
        nvd3dumx,nvwgf2umx,nvwgf2umx nvd3dum,nvwgf2um,nvwgf2um

        Adapter Drivers (GPU #2)
        igdumd64 igd10umd64 igd10umd64 igdumd32 igd10umd32 igd10umd32

        Adapter RAM
        256

        Adapter RAM (GPU #2)
        Unknown

        ClearType Parameters
        DISPLAY1 [ Gamma: 2200 Pixel Structure: RGB ClearType Level: 100 Enhanced Contrast: 50 ] DISPLAY2 [ Gamma: 2200 Pixel Structure: RGB ClearType Level: 100 Enhanced Contrast: 50 ] DISPLAY3 [ Gamma: 2200 Pixel Structure: RGB ClearType Level: 100 Enhanced Contrast: 50 ]

        Device ID
        0x0422

        Device ID (GPU #2)
        0x0162

        Direct2D Enabled
        true

        DirectWrite Enabled
        true (6.2.9200.16492)

        Driver Date
        1-18-2013

        Driver Date (GPU #2)
        12-12-2012

        Driver Version
        9.18.13.1106

        Driver Version (GPU #2)
        9.17.10.2932

        GPU #2 Active
        false

        GPU Accelerated Windows
        1/1 Direct3D 10

        Vendor ID
        0x10de

        Vendor ID (GPU #2)
        0x8086

        WebGL Renderer
        Google Inc. -- ANGLE (NVIDIA GeForce 8400 GS )

        AzureCanvasBackend
        direct2d

        AzureContentBackend
        direct2d

        AzureFallbackCanvasBackend
        cairo

Comment 2

[Matt Woodrow (:mattwoodrow)]

about:support should work if you run it in the first tab (which runs in the main process iirc)

I'm guessing that you're getting the d3d11 compositor though, since you get d2d/d3d10 normally.

Bas: Would you expect popups to be broken with d3d11 compositing?

Comment 3

[Mark Hammond [:markh] [:mhammond] [PTO until Sept 7]]

(In reply to Matt Woodrow (:mattwoodrow) from comment #2)
> about:support should work if you run it in the first tab (which runs in the
> main process iirc)

You are probably correct about the first-tab running in the main process - only when I open a second tab do I get a plugin-container child process.

But almost no about: stuff works in that first tab - certainly about:support and about:config don't.  about:home does - IIRC, that doesn't run with chrome permissions.  As soon as I attempt to open, say, about:support, the tab gets the title ("Troubleshooting Information") with the loading spinner, but the content area remains blank.  Once things are in this state, all other attempts to load regular content also fail (title and spinner remain "stuck", content area remains empty).

Also, the "Error Console" has significant display problems - as soon as you scroll (almost) everything goes blank for a few seconds then magically comes back (even without any further interaction with it).  Clearly the error console isn't running in a remote process, so I suspect the issue has nothing to do with remote tabs as such, but more the other side-effects of setting that pref (eg, does that force OMTC on?).

FWIW, I just tried the same thing under a Windows 7 x64 VM and get exactly the same symptoms.  The graphics properties when running the same build under the VM are:

Adapter Description: VMware SVGA 3D (Microsoft Corporation - WDDM)
Adapter Drivers: vm3dum64 vm3dum vm3dgl64 vm3dgl
Adapter RAM: 128
Device ID: 0x0405
Direct2D Enabled: Blocked for your graphics card because of unresolved driver issues.
DirectWrite Enabled: false (6.2.9200.16492)
Driver Date: 11-11-2011
Driver Version: 7.14.1.1134
GPU #2 Active: false
GPU Accelerated Windows: 0/2 Basic Blocked for your graphics card because of unresolved driver issues.
Vendor ID: 0x15ad
WebGL Renderer: Blocked for your graphics card because of unresolved driver issues.
AzureCanvasBackend: skia
AzureContentBackend: none
AzureFallbackCanvasBackend: cairo

Comment 4

[Timothy Nikkel (:tnikkel)]

Random guess: do the native parents and nsIWidget parents of the widgets for the popup get set correctly? Not sure if that would cause a problem if they weren't.

Comment 5

[Virtual_ManPL [:Virtual] 🇵🇱 - (please needinfo? me - so I will see your comment/message/reply/question/etc.)]

browser.tabs.remote was removed in bug #1072417,
so I'm closing this one as RESOLVED WORKSFORME.
If you think otherwise, please reopen this bug.

Comment 6

[Virtual_ManPL [:Virtual] 🇵🇱 - (please needinfo? me - so I will see your comment/message/reply/question/etc.)]

More FYI - If you can still reproduce the problem after enabling e10s now with:
-browser.tabs.remote.autostart=true or browser.tabs.remote.autostart.1=true
-browser.tabs.remote.desktopbehavior=true
please reopen this bug.

Comment 7

[Mark Hammond [:markh] [:mhammond] [PTO until Sept 7]]

WFM too.