[Webkit-unassigned] [Bug 167605] New: [GTK] Environment variables for enabling/disabling AC mode should take precedence over the API.

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=167605

            Bug ID: 167605
           Summary: [GTK] Environment variables for enabling/disabling AC
                    mode should take precedence over the API.
    Classification: Unclassified
           Product: WebKit
           Version: WebKit Nightly Build
          Hardware: Unspecified
                OS: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: WebKit Gtk
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: clopez at igalia.com
                CC: bugs-noreply at webkitgtk.org
            Blocks: 167509

After r211363 <http://trac.webkit.org/r211363> the WEBKIT_DISABLE_COMPOSITING_MODE environment variable not longer works as one should expect.

Not sure if this was intentional or not.

But I think we should bring back this environment variable, and make it take precedence over any API setting that the application defines.


This is useful for the following use cases:

 * Testing if disabling AC makes a difference without having to rebuild the application to add a different API call. 
 * Letting the user override the application acceleration hardware policy, which is useful when the user has a broken graphics drivers, and despite of that wants to use a WebKitGTK+ based application that enables AC mode by default (or that enables it ondemand).

    - For example, users of nvidia binary graphics drivers right now can only use Epiphany flatpaks with this environment variable. Otherwise the browser will crash when trying to enter into AC mode. And I don't expect Epiphany to disable AC.

    - So with this at least the user can use this environment variable at runtime to override the HW policy settings of the application 



And the same for the other variable WEBKIT_FORCE_COMPISITING_MODE

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-unassigned/attachments/20170130/381d46f0/attachment.html>