- 03 Apr, 2014 40 commits
-
-
sky@chromium.org authored
BUG=none TEST=none R=darin@chromium.org, jam@chromium.org Review URL: https://codereview.chromium.org/220073002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@261519 0039d316-1c4b-4281-b951-d872f2087c98
-
mukai@chromium.org authored
It was added for some experiments, but it's over. We don't need this flag anymore. Even when we really want to do this in the future, the code base would be quite different and this would not be reused. BUG=None TBR=xiyuan@chromium.org Review URL: https://codereview.chromium.org/217423002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@261518 0039d316-1c4b-4281-b951-d872f2087c98
-
guohui@chromium.org authored
For mock please see slides 8-19 at https://docs.google.com/a/google.com/presentation/d/1UMAexroivw01osOXpnEqbQcE3FMyDkc9eZoIszm4DP4/edit#slide=id.g12716c62f_064 Snapshot at https://x20web.corp.google.com/~guohui/remove_secondary_mac.png https://x20web.corp.google.com/~guohui/remove_primary_mac.png https://x20web.corp.google.com/~guohui/signin_title_mac.png BUG=345075, 354462 R=asvitkine@chromium.org, noms@chromium.org Review URL: https://codereview.chromium.org/220163007 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@261517 0039d316-1c4b-4281-b951-d872f2087c98
-
thakis@chromium.org authored
BUG=120677 NOTRY=true Review URL: https://codereview.chromium.org/224183002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@261516 0039d316-1c4b-4281-b951-d872f2087c98
-
mark@chromium.org authored
The message that this presents is: Chromium wants to use your confidential information stored in “Chrome Safe Storage” in your keychain. Do you want to allow access to this item? Chromium shouldn't ask for access to Google Chrome's data, it should have its own Chromium Safe Storage item in the keychain. R=isherman@chromium.org Review URL: https://codereview.chromium.org/200623002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@261515 0039d316-1c4b-4281-b951-d872f2087c98
-
thakis@chromium.org authored
Depends on https://chrome-internal-review.googlesource.com/159155 BUG=330631 NOTRY=true Review URL: https://codereview.chromium.org/223073002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@261509 0039d316-1c4b-4281-b951-d872f2087c98
-
sky@chromium.org authored
Nothing substantial here, just some name changes and other random cleanup. BUG=none TEST=none R=pkotwicz@chromium.org Review URL: https://codereview.chromium.org/215973006 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@261508 0039d316-1c4b-4281-b951-d872f2087c98
-
stepco@chromium.org authored
The cloud policy refresh scheduler no longer waits for policy invalidations to become available before issuing the first policy fetch. We want to ensure that any policy change that results from this initial policy fetch is counted as a change without invalidations enabled for metrics purposes. Currently we determine if invalidations are enabled based on whether the invalidation service has reported that it is on. However, there may be a delay between the invalidation service being enabled and the invalidation service actually delivering a pending invalidation. Additionally, on Android the invalidation service always reports that it is enabled. To account for this, add a "grace period" after the invalidation service is enabled during which we still consider invalidations disabled for metrics reporting. BUG=355884 Review URL: https://codereview.chromium.org/213743014 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@261506 0039d316-1c4b-4281-b951-d872f2087c98
-
jracle@logitech.com authored
Fix : HidConnectionLinux::FindHidrawDevNode should look for presence of "hidraw" string immediately after matching parent udev path, so that we do not match devnodes created by bus enumerator driver BUG=358666 TBR=rockot@chromium.org Review URL: https://codereview.chromium.org/223803002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@261502 0039d316-1c4b-4281-b951-d872f2087c98
-
jamescook@chromium.org authored
This is a step toward moving it into //apps where it can be used by app_shell BUG=359126 TEST=browser_tests PlatformApp* TBR=miket@chromium.org for DEPS Review URL: https://codereview.chromium.org/214243003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@261501 0039d316-1c4b-4281-b951-d872f2087c98
-
petewil@chromium.org authored
To unlock features with seen/unseen state, hidpi screens, and locale awareness, update to the latest version of the protobuf used by the server side. BUG=305901 Review URL: https://codereview.chromium.org/217203003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@261499 0039d316-1c4b-4281-b951-d872f2087c98
-
hshi@chromium.org authored
The I420 and YV12 formats both are almost identical except for the order of U and V planes in memory. They are effectively the same for renderers that access U and V plane data via MediaFrame::data(size_t plane). BUG=341452 BUG=355763 TEST=trybot R=danakj@chromium.org, dmichael@chromium.org, fischman@chromium.org, perkj@chromium.org, piman@chromium.org Review URL: https://codereview.chromium.org/222563002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@261497 0039d316-1c4b-4281-b951-d872f2087c98
-
jyasskin@chromium.org authored
Thanks to ncarter for the test! BUG=357382 Review URL: https://codereview.chromium.org/216113007 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@261496 0039d316-1c4b-4281-b951-d872f2087c98
-
dmazzoni@chromium.org authored
When the aura Window containing the RWHVA gets or loses focus, we must fire the corresponding accessibility event on that object, which corresponds to the root "document" in the web hierarchy. This worked before the Aura switch because native HWNDs fired these events automatically. BUG=347448 Review URL: https://codereview.chromium.org/214243005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@261495 0039d316-1c4b-4281-b951-d872f2087c98
-
sandersd@chromium.org authored
This is the first part of work to remove byte range computations out of media::Pipeline, and instead have the DataSource report those directly to Pipeline's parent, which will avoid crossing thread boundaries unnecessarily. This first CL just cleans up the interfaces required to do that, but already eliminates some of the stranger parts of the set-up code. BUG=122071 Review URL: https://codereview.chromium.org/212803004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@261494 0039d316-1c4b-4281-b951-d872f2087c98
-
yefim@chromium.org authored
> Disabled context menu for external component extension icon on MAC (to be consistent with Windows). > > BUG=354923 > > Review URL: https://codereview.chromium.org/197333005 TBR=yefim@chromium.org Review URL: https://codereview.chromium.org/224013005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@261493 0039d316-1c4b-4281-b951-d872f2087c98
-
chrome-admin@google.com authored
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@261492 0039d316-1c4b-4281-b951-d872f2087c98
-
eseidel@chromium.org authored
TBR= BUG= Review URL: https://codereview.chromium.org/223783004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@261491 0039d316-1c4b-4281-b951-d872f2087c98
-
nick@chromium.org authored
Reason for re-land: Change was found not guilty; charges were dropped. > Revert 261380 "cc: Remove TextureLayer::SetTextureId and Texture..." > > [Reason for revert: failure in WindowUtilTest.RecreateLayers > in test suite wm_core_unittests > on bot Linux ChromiumOS Tests (dbg)(1) Build] > > > cc: Remove TextureLayer::SetTextureId and TextureLayer::WillModifyTexture > > > > These are not used anymore except for clearing the client-provided texture, so > > this removes 1 of 4 TextureLayer paths, and simplifies externally-exposed state. > > > > BUG=337922 > > > > Review URL: https://codereview.chromium.org/213743005 > > TBR=piman@chromium.org > > Review URL: https://codereview.chromium.org/224153003 TBR=nick@chromium.org Review URL: https://codereview.chromium.org/224363003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@261490 0039d316-1c4b-4281-b951-d872f2087c98
-
bruening@google.com authored
TBR=zhaoqin@chromium.org BUG=https://code.google.com/p/drmemory/issues/detail?id=1052#c56 Review URL: https://codereview.chromium.org/224303003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@261489 0039d316-1c4b-4281-b951-d872f2087c98
-
rvargas@chromium.org authored
BUG=322664 Review URL: https://codereview.chromium.org/212603021 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@261488 0039d316-1c4b-4281-b951-d872f2087c98
-
jracle@logitech.com authored
- Read (Input callback) : report ID is already contained in input buffer... - Write : append report ID to payload, to be consistent with other platforms BUG=358686 TBR=rockot@chromium.org Review URL: https://codereview.chromium.org/223793002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@261487 0039d316-1c4b-4281-b951-d872f2087c98
-
rch@chromium.org authored
R=rtennet@chromium.org BUG= Review URL: https://codereview.chromium.org/216553008 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@261486 0039d316-1c4b-4281-b951-d872f2087c98
-
wolenetz@chromium.org authored
In preparation for landing the new FrameProcessor, this change parameterizes WebMediaSourceImpl::addSourceBuffer() and ChunkDemuxer::AddId() to select which of legacy or new processor to use to process frames appended to the source buffer. This change also parameterizes ChunkDemuxerTests and the MSE subset of PipelineIntegrationTests to allow testing of both frame processors in the short term until the new processor has landed and stabilized enough. Since the MSE WebSourceBuffer API for Chromium platform in Blink is not yet stabilized, this change also removes related OVERRIDEs. R=acolwell@chromium.org BUG=249422 TEST=All media unittests pass locally on Linux with ChromeOS ffmpeg branding and proprietary codecs enabled, and no local MSE layout test regression Review URL: https://codereview.chromium.org/220113002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@261485 0039d316-1c4b-4281-b951-d872f2087c98
-
chrome-admin@google.com authored
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@261484 0039d316-1c4b-4281-b951-d872f2087c98
-
mallinath@chromium.org authored
Failing on all bots (http://build.chromium.org/p/chromium.linux/builders/Linux%20Tests/builds/10031) > Update V8 to version 3.26.5 (based on bleeding_edge revision r20452). > > TBR=jochen@chromium.org > NOTRY=true > > Review URL: https://codereview.chromium.org/223403002 TBR=machenbach@chromium.org Review URL: https://codereview.chromium.org/222583004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@261483 0039d316-1c4b-4281-b951-d872f2087c98
-
antrim@chromium.org authored
R=nkostylev@chromium.org TBR=bauerb@chromium.org BUG=282464 Review URL: https://codereview.chromium.org/220913003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@261482 0039d316-1c4b-4281-b951-d872f2087c98
-
jackhou@chromium.org authored
The UpdateShortcutWorker class is windows specific and is moved to its own file. UpdateShortcutForTabContents is moved to web_app_win. GetShortcutInfoForTab is moved to web_app. TBR=sky@chromium.org BUG=356889 Review URL: https://codereview.chromium.org/213113005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@261481 0039d316-1c4b-4281-b951-d872f2087c98
-
earthdok@chromium.org authored
BUG=354644, 356306 TBR=glider@chromium.org Review URL: https://codereview.chromium.org/224013004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@261480 0039d316-1c4b-4281-b951-d872f2087c98
-
mpcomplete@chromium.org authored
collected, rather than a raw integer. BUG=357785 Review URL: https://codereview.chromium.org/214183003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@261479 0039d316-1c4b-4281-b951-d872f2087c98
-
denniskempin@chromium.org authored
In order to support mice via CMT (Project Cobra) we will have to do the natural scroll handling in the CMT driver instead of Chrome. BUG=chromium:285663 TEST=test with touchpads and traditional mice. Everything should work as before, touchpad should have natural scroll applied, scroll wheels should not. Test changing the natural scroll property and see if it's applied correctly. Also test if touch mice have natural scroll applied. Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=260926 Review URL: https://codereview.chromium.org/212603005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@261478 0039d316-1c4b-4281-b951-d872f2087c98
-
jennyz@chromium.org authored
BUG=359213 R=xiyuan@chromium.org Review URL: https://codereview.chromium.org/221903007 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@261477 0039d316-1c4b-4281-b951-d872f2087c98
-
tfarina@chromium.org authored
Two function were hidden under chromeos ifdef, since they are called only on ChromeOS and one constant were also hidden under chromeos ifdef for the same reason. BUG=None TEST=./build/gyp_chromium -Duse_aura, ninja -C out/Debug ash_unittests R=jamescook@chromium.org Review URL: https://codereview.chromium.org/222963003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@261476 0039d316-1c4b-4281-b951-d872f2087c98
-
chrome-admin@google.com authored
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@261475 0039d316-1c4b-4281-b951-d872f2087c98
-
andrewhayden@chromium.org authored
Fixes for: https://code.google.com/p/cld2/issues/detail?id=11 https://code.google.com/p/cld2/issues/detail?id=12 BUG= Review URL: https://codereview.chromium.org/213623003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@261474 0039d316-1c4b-4281-b951-d872f2087c98
-
mukai@chromium.org authored
Moves the transient parent utilities to gtk2_util and makes both dialogs use it. This is a reland of r259318 with a fix of test failures. BUG=334331 TBR=erg@chromium.org TEST=manually Review URL: https://codereview.chromium.org/221813010 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@261473 0039d316-1c4b-4281-b951-d872f2087c98
-
jiayl@chromium.org authored
The timestamp generation is moved from libjingle/renderer to the browser. The renderer sends the absolute system time for each message in the IPC, which is used by WebRtcLoggingHandlerHost to calculate the timestamp relative to the logging started time. BUG=339478 Review URL: https://codereview.chromium.org/218403004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@261472 0039d316-1c4b-4281-b951-d872f2087c98
-
jdduke@chromium.org authored
Revert of [Android] Provide unhandled tap event notifications (https://codereview.chromium.org/218633008/) Reason for revert: Legitimate browsertest failure. Original issue's description: > [Android] Provide unhandled tap event notifications > > Allow notifications of unhandled taps via the GestureStateListener. This change > makes GestureTap events blocking, but there are several use-cases for which this > will be necessary, e.g., WebView and contextual search. > > NOTRY=true > > Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=261431 TBR=mkosiba@chromium.org,donnd@chromium.org,tedchoc@chromium.org NOTREECHECKS=true NOTRY=true Review URL: https://codereview.chromium.org/224273002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@261470 0039d316-1c4b-4281-b951-d872f2087c98
-
zea@chromium.org authored
The sync engine/api won't act on them yet; this just lays the groundwork for passing context changes around. BUG=345420 Review URL: https://codereview.chromium.org/220043002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@261469 0039d316-1c4b-4281-b951-d872f2087c98
-
noyau@chromium.org authored
This is not used for anything anymore. BUG=None Review URL: https://codereview.chromium.org/223813003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@261467 0039d316-1c4b-4281-b951-d872f2087c98
-