| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This handles a corner case where all broker resources are deleted before the channel created IPC response is handled or if it never occurs. This doesn't solve all potential problems, but it helps with the ones we can influence.
An example scenario that this does not fix is if another broker resource is created by the plugin in the same renderer but the broker process is hung or thinks it has a channel to this renderer (channel names are based on the renderer). Even though a new PpapiBrokerImpl will be created as expected, the broker will not establish the channel.
BUG=81335
TEST=none
Review URL: http://codereview.chromium.org/6883101
TBR=ddorwin@chromium.org
Review URL: http://codereview.chromium.org/6913034
git-svn-id: svn://svn.chromium.org/chrome/branches/742/src@83958 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Disconnect calls.
Previously, the PluginModule still had a reference to the PpapiBrokerImpl, so the broker channel was not destroyed until the module was. Now, it is destroyed when the instance is or a plugin releases all references to PPB_BrokerTrusted.
This change also makes the PpapiBrokerImpl's reference to PPB_Broker_Impl a WeakPtr so that the PPB_Broker_Impl can be destroyed even if the PpapiBrokerImpl is not. This prevents a scenario where neither would be destroyed if the broker channel was never established and pending_connects_ was never cleared.
BUG=81335
TEST=Add the following to the PPB_BrokerTrusted::Connect callback: pp::Module::Get()->core()->ReleaseResource(broker_resource);. The broker process should exit in 30 seconds while the plugin process keeps running.
Review URL: http://codereview.chromium.org/6881033
TBR=ddorwin@chromium.org
git-svn-id: svn://svn.chromium.org/chrome/branches/742/src@83956 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
the fact that worker thread actually run in a different renderer process from the main page JS thread. chrome.fileBrowserPrivate.* methods grant access to files through ChildProcessSecurityPolicy class, but such file permissions would end up associated with renderer process of the main thread only. When worker tries to register blobs representing such files, ChildProcessSecurityPolicy check would reject it since its client process id has nothing to do with main renderer's id.
This CL adds mapping between worker and main renderer processes and uses that to ensure that worker thread renderer process file permissions are "inherited" from its main JS thread renderer child process.
BUG=chromium-os:14680
TEST=added extra tests to ChildProcessSecurityPolicyTest.FilePermissions
Review URL: http://codereview.chromium.org/6893145
TBR=zelidrag@chromium.org
Review URL: http://codereview.chromium.org/6912001
git-svn-id: svn://svn.chromium.org/chrome/branches/742/src@83772 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
| |
Review URL: http://codereview.chromium.org/6904083
TBR=cevans@chromium.org
Review URL: http://codereview.chromium.org/6883243
git-svn-id: svn://svn.chromium.org/chrome/branches/742/src@83396 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
| |
Removed "compositor" child window that was created by the GPU process.Removed the sync IPC that it used to ask the browser process to resize on Linux. Adapted windows to use the same mechanism.TEST=test webgl pages on windows (ANGLE and GL), linux and mac, run try job on windows, linux, mac. checkdeps failure look unrelated to patch.
BUG=77536
Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=83248
git-svn-id: svn://svn.chromium.org/chrome/branches/742/src@83276 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
| |
Review URL: http://codereview.chromium.org/6877028
BUG=78189
TBR=nduca@chromium.org
Review URL: http://codereview.chromium.org/6883207
git-svn-id: svn://svn.chromium.org/chrome/branches/742/src@83260 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
deadlock.
I patched in Jonathan's change from http://codereview.chromium.org/6881105/ for the CreateViewCommandBuffer message, and also added the Synchronize and EstablishChannel. The latter required making GpuDataManager callable from the IO thread. I moved the code that loads the blacklist from the prefs and web to Chrome code, since I wanted to do that anyways so that GpuProcessHostUIShim and GpuDataManager can move to content (I'll do that later).
Since the messages are filtered on the IO thread, it's now GpuProcessHost that creates GpuProcessHostUIShim. Accordingly, all the code that used to call GpuProcessHostUIShim to send a message now has to call GpuProcessHost, since the logic of when to create a process is there. Also, since there's no IO thread object for the in-process case, I've had to break that in the meantime. Al will take a look at that later.
BUG=77536
Review URL: http://codereview.chromium.org/6902021
TBR=jam@chromium.org
Review URL: http://codereview.chromium.org/6902087
git-svn-id: svn://svn.chromium.org/chrome/branches/742/src@83219 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
| |
RedirectToFileResourceHandler::OnRequestClosed() if the request is closed before the temporary file is created.BUG=79099TEST=See http://crbug.com/79099#c4.Review URL: http://codereview.chromium.org/6905008
TBR=eroman@chromium.org
git-svn-id: svn://svn.chromium.org/chrome/branches/742/src@83217 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
| |
mistake in the volume meter image.BUG=noneTEST=manual, test speech input with some profanity and verify that the censored words have all but the first letter shown as '*'Review URL: http://codereview.chromium.org/6901050
TBR=satish@chromium.org
git-svn-id: svn://svn.chromium.org/chrome/branches/742/src@83170 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
| |
current codecan't run in the sandbox on Linux.TEST=manualBUG=80176Review URL: http://codereview.chromium.org/6891001
TBR=brettw@chromium.org
TEST=80176
Review URL: http://codereview.chromium.org/6899026
git-svn-id: svn://svn.chromium.org/chrome/branches/742/src@82655 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
condition.
NSExceptions can cause the flag to get latched to YES, which
messeswith window closing. A number of suspected exceptions shouldn't
causetoo much other damage, so this patches over the problem for the
shortterm.
TBR=jam@chromium.org
BUG=45928
TEST=see bug
Review URL: http://codereview.chromium.org/6873081
TBR=shess@chromium.org
Review URL: http://codereview.chromium.org/6883130
git-svn-id: svn://svn.chromium.org/chrome/branches/742/src@82539 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
| |
provider.Per Eric's request, refactored FileSystemDirURLRequestJob and FileSystemURLRequestJob classes to resolve local file system through a new operation.BUG=chromium-os:14225TEST=added new test cases to FileSystemPathManagerTest.*, added FileSystemOperationTest.TestGetLocalFilePathSuccessReview URL: http://codereview.chromium.org/6864040
TBR=zelidrag@chromium.org
Review URL: http://codereview.chromium.org/6882102
git-svn-id: svn://svn.chromium.org/chrome/branches/742/src@82372 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
| |
and PDFs in iframe.BUG=79840TEST=Verify embedded PDFs can save using toolbar (lower-right corner).Review URL: http://codereview.chromium.org/6881055
TBR=gene@chromium.org
Review URL: http://codereview.chromium.org/6877097
git-svn-id: svn://svn.chromium.org/chrome/branches/742/src@82369 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
| |
update the expectation upstream.
R=abarth
Review URL: http://codereview.chromium.org/6879074
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@82246 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
| |
content with ResourceContext
BUG=78596
TEST=none
Review URL: http://codereview.chromium.org/6882016
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@82219 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I split the IPC up into two parts on Linux--one that reads the image on the UI
thread, and a second part that encodes the image on the file thread before
replying. I've also switched it to send the data over shared memory instead of passing a (potentially) huge blob of data over IPC.
BUG=75237
TEST=Local testing.
Review URL: http://codereview.chromium.org/6871001
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@82212 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
| |
Go through IO Registry to locate PCI based video cards on Mac. If there are two video cards and one of them is Intel, we assume Intel GPU is the integrated one and the other is the discrete one. Chromium GPU process should always use the discrete one (if Mac is handling automatic card switching), and we identify the discrete card in preliminary GPU info collection so we could run through GPU software rendering list and set up the renderer process with approriate GPU feature capabilities.
Note that if the IO registry method fails, we fallback to the original "GPU locating through current display" method, so this CL should be pretty safe.
BUG=75208,75220
TEST=gpu acceleration is enabled on Mac with Intel/ATI dual GPU.
Review URL: http://codereview.chromium.org/6879023
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@82202 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
| |
BUG=None
TEST=None
Review URL: http://codereview.chromium.org/6879042
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@82198 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
| |
BUG=None
TEST=Unittests
Review URL: http://codereview.chromium.org/6840033
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@82190 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
| |
BUG=chromium:79777
TEST=See issue
TBR=avi
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@82176 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This first thing this CL does is plumbs through the surface that the GPU will eventually render to very early on (with the ViewMsg_New and ViewMsg_CreateNew IPCs). Previously, these surfaces were acquired at the time that GPU got a request for a command buffer. This required mediation by the browser UI thread. With this CL, we pre-acquire the surfaces so that they can be passed with the request for the command buffer. This will allow us to handle the request on the browser IO thread.
The second thing this CL does is change the surface management a bit. When surfaces were acquired and released when command buffers were created and destroyed, the GPU process host was natural manager of surfaces. This pushes the management further down into the RWHV level and GtkNativeViewManager (on Linux). It fixes a minor resource leak.
BUG=first stage of 77536
TEST=By hand WebGL, 3D CSS, Pepper 3D on Linux, Windows, and Mac.
Review URL: http://codereview.chromium.org/6840060
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@82165 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
BUG=26339
TEST=unit_tests.exe, sync_integration_tests.exe, sync_unit_tests.exe. manual testcases:
1. Set up a brand new profile to sync and make sure it syncs.
2. enable/disable a datatype and make sure it syncs.
3. Make change to a datatype locally and make sure it gets propagated.
4. make change to a datatype remotely and make sure it syncs down.
Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=82026
Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=82067
Review URL: http://codereview.chromium.org/6874018
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@82150 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
| |
This allows the PNG compression to be offloaded to another thread as
appropriate.
BUG=75237
TEST=Local testing.
Review URL: http://codereview.chromium.org/6835036
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@82142 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
| |
in order to match the change in bugs.webkit.org/show_bug.cgi?id=58401
BUG=58977
TEST=drag a folder onto a webkitdirectory control
Review URL: http://codereview.chromium.org/6873069
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@82130 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
| |
process. Added more trace events to show expensive blocking IPCs in renderer process.
BUG=79510
TEST=start trace in about:gpu; open some WebGL windows; when trace Buffer usage reaches 100%, verify that the trace is ended
Review URL: http://codereview.chromium.org/6870020
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@82115 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
| |
BUG=none
TEST=none
Review URL: http://codereview.chromium.org/6879005
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@82098 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
| |
that failed.BUG=26339TEST=unit_tests.exe, sync_integration_tests.exe, sync_unit_tests.exe. manual testcases:1. Set up a brand new profile to sync and make sure it syncs.2. enable/disable a datatype and make sure it syncs.3. Make change to a datatype locally and make sure it gets propagated.4. make change to a datatype remotely and make sure it syncs down.Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=82026Review URL: http://codereview.chromium.org/6874018
TBR=lipalani@chromium.org
Review URL: http://codereview.chromium.org/6883037
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@82073 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
| |
a minor issue whereby failure to set a cookie "Secure" can get leaked via
a WebSocket when http itself is mitiagted.
TEST=WebSocketJobTest.HSTSUpgrade
Review URL: http://codereview.chromium.org/6873029
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@82069 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
| |
BUG=None
TEST=None
Review URL: http://codereview.chromium.org/6831021
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@82068 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
BUG=26339
TEST=unit_tests.exe, sync_integration_tests.exe, sync_unit_tests.exe. manual testcases:
1. Set up a brand new profile to sync and make sure it syncs.
2. enable/disable a datatype and make sure it syncs.
3. Make change to a datatype locally and make sure it gets propagated.
4. make change to a datatype remotely and make sure it syncs down.
Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=82026
Review URL: http://codereview.chromium.org/6874018
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@82067 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
| |
that failed.BUG=26339TEST=unit_tests.exe, sync_integration_tests.exe, sync_unit_tests.exe. manual testcases:1. Set up a brand new profile to sync and make sure it syncs.2. enable/disable a datatype and make sure it syncs.3. Make change to a datatype locally and make sure it gets propagated.4. make change to a datatype remotely and make sure it syncs down.Review URL: http://codereview.chromium.org/6874018
TBR=lipalani@chromium.org
Review URL: http://codereview.chromium.org/6877027
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@82040 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
| |
Review URL: http://codereview.chromium.org/6877019
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@82037 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
| |
BUG=79632
TEST=run trace in about:gpu; observe the number of times the GPU process sequentially calls WaitLatch; verify it is not spinning.
Review URL: http://codereview.chromium.org/6874029
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@82033 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
| |
pages. In particular it waspossible for an error page load to cancel a navigation.BUG=79515TEST=noneR=darin@chromium.orgReview URL: http://codereview.chromium.org/6865031TBR=sky@chromium.orgReview URL: http://codereview.chromium.org/6881026
TBR=sky@chromium.org
Review URL: http://codereview.chromium.org/6878034
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@82031 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
| |
This only handles Linux. Win uses a modal dialog instead of a tab-constrained dialog, and will require a different approach. Mac has issues with programmatically closing its native sheet.
BUG=73223
TEST=see bug
Review URL: http://codereview.chromium.org/6812033
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@82030 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
BUG=26339
TEST=unit_tests.exe, sync_integration_tests.exe, sync_unit_tests.exe. manual testcases:
1. Set up a brand new profile to sync and make sure it syncs.
2. enable/disable a datatype and make sure it syncs.
3. Make change to a datatype locally and make sure it gets propagated.
4. make change to a datatype remotely and make sure it syncs down.
Review URL: http://codereview.chromium.org/6874018
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@82026 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
| |
it waspossible for an error page load to cancel a navigation.BUG=79515TEST=noneR=darin@chromium.orgReview URL: http://codereview.chromium.org/6865031
TBR=sky@chromium.org
Review URL: http://codereview.chromium.org/6881026
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@82018 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
| |
renderer exits.
BUG=none
TEST=none
Review URL: http://codereview.chromium.org/6882020
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@82017 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is a list of strings. Any protocol scheme listed in this policy is
disabled, and URLs using that scheme won't load (either from the Omnibar, links,
bookmarks, or when requested from the renderer to the browser).
Also introduced ListPrefMember, to track a ListValue preference.
"Virtual" or "pseudo" protocol schemes such as "about" and "view-source" are
also handled.
BUG=57477
TEST=unit_tests, use a policy to disable specific schemes (e.g. "file", "ftp")
Review URL: http://codereview.chromium.org/6712065
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@82013 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
| |
Instead, return them to the caller and let the caller decide whether
the error is worth notifying the user about.
BUG=79068
Review URL: http://codereview.chromium.org/6864020
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@82008 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
| |
tighten a little in device_orientation.
Review URL: http://codereview.chromium.org/6883022
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@82001 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
| |
serialization code, and move the icon messages there. Also get rid of friend class in RenderView that's not needed anymore.
Review URL: http://codereview.chromium.org/6883020
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@81999 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
| |
possible for an error page load to cancel a navigation.
BUG=79515
TEST=none
R=darin@chromium.org
Review URL: http://codereview.chromium.org/6865031
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@81994 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
| |
gpu/plugin/worker directories as well.
I've moved the breakpad specific code out of content\renderer\renderer_main.cc into chrome\renderer\chrome_render_process_observer.cc. I've also moved the rest of the process-specific initialization from chrome_content_renderer_client.cc there as well, so that all the chrome renderer process init code is one place (some of it existed before chrome_render_process_observer.cc was created).
Review URL: http://codereview.chromium.org/6884001
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@81979 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
| |
plumbs through the surface that the GPU will eventually render to very early on (with the ViewMsg_New and ViewMsg_CreateNew IPCs). Previously, these surfaces were acquired at the time that GPU got a request for a command buffer. This required mediation by the browser UI thread. With this CL, we pre-acquire the surfaces so that they can be passed with the request for the command buffer. This will allow us to handle the request on the browser IO thread.The second thing this CL does is change the surface management a bit. When surfaces were acquired and released when command buffers were created and destroyed, the GPU process host was natural manager of surfaces. This pushes the management further down into the RWHV level and GtkNativeViewManager (on Linux). It fixes a minor resource leak.BUG=first stage of 77536TEST=By hand WebGL, 3D CSS, Pepper 3D on Linux, Windows, and Mac.Review URL: http://codereview.chromium.org/6840060
TBR=backer@chromium.org
Review URL: http://codereview.chromium.org/6878021
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@81974 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
| |
TEST=compiles
BUG=None
Review URL: http://codereview.chromium.org/6870021
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@81966 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This first thing this CL does is plumbs through the surface that the GPU will eventually render to very early on (with the ViewMsg_New and ViewMsg_CreateNew IPCs). Previously, these surfaces were acquired at the time that GPU got a request for a command buffer. This required mediation by the browser UI thread. With this CL, we pre-acquire the surfaces so that they can be passed with the request for the command buffer. This will allow us to handle the request on the browser IO thread.
The second thing this CL does is change the surface management a bit. When surfaces were acquired and released when command buffers were created and destroyed, the GPU process host was natural manager of surfaces. This pushes the management further down into the RWHV level and GtkNativeViewManager (on Linux). It fixes a minor resource leak.
BUG=first stage of 77536
TEST=By hand WebGL, 3D CSS, Pepper 3D on Linux, Windows, and Mac.
Review URL: http://codereview.chromium.org/6840060
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@81965 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
| |
Review URL: http://codereview.chromium.org/6878002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@81962 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
| |
(NaCl, registration of Chrome plugins like pdf/remoting/flash) behind.
Review URL: http://codereview.chromium.org/6869051
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@81959 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The previous implementation of status was tied to the features that the blacklist understood. This limited our expressiveness about the status of user-facing features. For example....
Before:
- Accelerated compositing: enabled/disabled/unavailable
After:
- 3D CSS: enabled, unavailable, disabled
- Compositing: software, software rendering due to gpu unavailable, softawre rendering due to being disabled, enabled
Key here is decoupling the features reported in the status from gpu blacklist features enum. On top of that, the states are expanded to show difference between off, off and falling back to software, and software rendering because it wasn't enabled.
Review URL: http://codereview.chromium.org/6870004
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@81957 0039d316-1c4b-4281-b951-d872f2087c98
|