- 22 Aug, 2014 40 commits
-
-
sadrul@chromium.org authored
BUG=403810 R=oshima@chromium.org Review URL: https://codereview.chromium.org/488093004 Cr-Commit-Position: refs/heads/master@{#291417} git-svn-id: svn://svn.chromium.org/chrome/trunk/src@291417 0039d316-1c4b-4281-b951-d872f2087c98
-
erikwright@chromium.org authored
Shell operations may cause 3rd-party shell extensions to be loaded into the calling process. Isolating them in a utility process protects the browser process from potential instability. BUG=73098 Review URL: https://codereview.chromium.org/487453002 Cr-Commit-Position: refs/heads/master@{#291416} git-svn-id: svn://svn.chromium.org/chrome/trunk/src@291416 0039d316-1c4b-4281-b951-d872f2087c98
-
stevenjb@chromium.org authored
This fixes a bug introduced in https://codereview.chromium.org/427903004 BUG=406114 R=pneubeck@chromium.org Review URL: https://codereview.chromium.org/492373002 Cr-Commit-Position: refs/heads/master@{#291415} git-svn-id: svn://svn.chromium.org/chrome/trunk/src@291415 0039d316-1c4b-4281-b951-d872f2087c98
-
danakj@chromium.org authored
TBR=piman@chromium.org BUG=169282 Review URL: https://codereview.chromium.org/488133004 Cr-Commit-Position: refs/heads/master@{#291414} git-svn-id: svn://svn.chromium.org/chrome/trunk/src@291414 0039d316-1c4b-4281-b951-d872f2087c98
-
tburkard@chromium.org authored
R=jkarlin@chromium.org, asvitkine@chromium.org Review URL: https://codereview.chromium.org/495953003 Cr-Commit-Position: refs/heads/master@{#291413} git-svn-id: svn://svn.chromium.org/chrome/trunk/src@291413 0039d316-1c4b-4281-b951-d872f2087c98
-
chrome-admin@google.com authored
Cr-Commit-Position: refs/heads/master@{#291412} git-svn-id: svn://svn.chromium.org/chrome/trunk/src@291412 0039d316-1c4b-4281-b951-d872f2087c98
-
https://codereview.chromium.org/491773002/jam@chromium.org authored
Undo Blink rolls before https://codereview.chromium.org/491773002/ since it's causing most android tryjobs to fail with that asssert. Review URL: https://codereview.chromium.org/501493002 Cr-Commit-Position: refs/heads/master@{#291411} git-svn-id: svn://svn.chromium.org/chrome/trunk/src@291411 0039d316-1c4b-4281-b951-d872f2087c98
-
rdevlin.cronin@chromium.org authored
BUG=166959 Review URL: https://codereview.chromium.org/495193004 Cr-Commit-Position: refs/heads/master@{#291410} git-svn-id: svn://svn.chromium.org/chrome/trunk/src@291410 0039d316-1c4b-4281-b951-d872f2087c98
-
xiyuan@chromium.org authored
Bluetooth detection on Mac triggers 500ms adapter polling and causes performance regression. Since Easy unlock is only offered on ChromeOS at the moment, disable Bluetooth detection for other platforms while the polling problem is investigated. BUG=404482,399067 Review URL: https://codereview.chromium.org/498453002 Cr-Commit-Position: refs/heads/master@{#291409} git-svn-id: svn://svn.chromium.org/chrome/trunk/src@291409 0039d316-1c4b-4281-b951-d872f2087c98
-
bartfab@chromium.org authored
If the recommended locales for a public session are invalid/unavailable, public sessions should default to the current UI language, not the locale that happens to be first in alphabetic order (Arabic for Chrome OS running in English). BUG=403550 TEST=Extended unit and browser tests Review URL: https://codereview.chromium.org/483523005 Cr-Commit-Position: refs/heads/master@{#291408} git-svn-id: svn://svn.chromium.org/chrome/trunk/src@291408 0039d316-1c4b-4281-b951-d872f2087c98
-
chrome-admin@google.com authored
Cr-Commit-Position: refs/heads/master@{#291407} git-svn-id: svn://svn.chromium.org/chrome/trunk/src@291407 0039d316-1c4b-4281-b951-d872f2087c98
-
derat@chromium.org authored
BUG=403571 TBR=davemoore@chromium.org Review URL: https://codereview.chromium.org/470953005 Cr-Commit-Position: refs/heads/master@{#291406} git-svn-id: svn://svn.chromium.org/chrome/trunk/src@291406 0039d316-1c4b-4281-b951-d872f2087c98
-
sky@chromium.org authored
BUG=392974 TEST=none R=darin@chromium.org Review URL: https://codereview.chromium.org/480663003 Cr-Commit-Position: refs/heads/master@{#291405} git-svn-id: svn://svn.chromium.org/chrome/trunk/src@291405 0039d316-1c4b-4281-b951-d872f2087c98
-
mkwst@chromium.org authored
TBR=finnur@chromium.org NOTRY=true Review URL: https://codereview.chromium.org/500543002 Cr-Commit-Position: refs/heads/master@{#291404} git-svn-id: svn://svn.chromium.org/chrome/trunk/src@291404 0039d316-1c4b-4281-b951-d872f2087c98
-
weiliangc@chromium.org authored
Move RenderPass::Id out of RenderPass and make it an isolated class called RenderPassId, so RenderPassDrawQuad and AppendQuadsData will not need to depend on entire RenderPass class. BUG=344962 Review URL: https://codereview.chromium.org/404563005 Cr-Commit-Position: refs/heads/master@{#291403} git-svn-id: svn://svn.chromium.org/chrome/trunk/src@291403 0039d316-1c4b-4281-b951-d872f2087c98
-
grunell@chromium.org authored
The stats is intended for the low latency case, hence removing other cases. NOTRY=true Review URL: https://codereview.chromium.org/486633003 Cr-Commit-Position: refs/heads/master@{#291402} git-svn-id: svn://svn.chromium.org/chrome/trunk/src@291402 0039d316-1c4b-4281-b951-d872f2087c98
-
avi@chromium.org authored
Revert of Keep a copy of page id in RenderViewHost. (patchset #1 of https://codereview.chromium.org/493853002/) Reason for revert: This hit canary and we're getting instrumented crashes. That's what we were looking for so let's back it out. Original issue's description: > Keep a copy of page id in RenderViewHost. > > This is an instrumented version of the patch that will be reverted in a few days. > This is meant to catch crashes in edge cases and log enough for us to repro > them. > > BUG=99379, 369661 > TEST=this is gonna crash for a few people > > Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=291077 TBR=rsesek@chromium.org,creis@chromium.org NOTREECHECKS=true NOTRY=true BUG=99379, 369661 Review URL: https://codereview.chromium.org/500533002 Cr-Commit-Position: refs/heads/master@{#291401} git-svn-id: svn://svn.chromium.org/chrome/trunk/src@291401 0039d316-1c4b-4281-b951-d872f2087c98
-
pkotwicz@chromium.org authored
BUG=405957 TEST=SplitViewControllerTest.SplitModeActivation Review URL: https://codereview.chromium.org/488153003 Cr-Commit-Position: refs/heads/master@{#291400} git-svn-id: svn://svn.chromium.org/chrome/trunk/src@291400 0039d316-1c4b-4281-b951-d872f2087c98
-
dconnelly@chromium.org authored
BUG=328847 Review URL: https://codereview.chromium.org/422233009 Cr-Commit-Position: refs/heads/master@{#291399} git-svn-id: svn://svn.chromium.org/chrome/trunk/src@291399 0039d316-1c4b-4281-b951-d872f2087c98
-
vasilii@chromium.org authored
Credential Management API is Javascript API that can be used by sites to sign user in or correctly store the credentials in the password manager. BUG=400674 Review URL: https://codereview.chromium.org/459103005 Cr-Commit-Position: refs/heads/master@{#291398} git-svn-id: svn://svn.chromium.org/chrome/trunk/src@291398 0039d316-1c4b-4281-b951-d872f2087c98
-
finnur@chromium.org authored
Revert 291214 "Fixes three crashes" in an attempt to find the cause of Athena related unit test failures on the ASAN bot. http://build.chromium.org/p/chromium.memory/buildstatus?builder=Linux%20Chromium%20OS%20ASan%20LSan%20Tests%20%283%29&number=2862 > Fixes three crashes > * AppListViewDelegate was accessing deleted search_provider. > * DeviceSocketListener::StopListening can happen after DeviceSocketManager is deleted > * Explicitly delete FilePathWatcher. This was causing > recursive callback to FilePathWatcherImpl::Cancel from > FilePathWatcherImpl::CancelOnMessageLoopThread, which > caused crash. > > > Clean ups > * change OnIO to OnFILE as they run on FILE thread. > * removed unused singleton related code. > > BUG=None > TEST=Run athena_main on desktop and close window. > > Review URL: https://codereview.chromium.org/490033003 TBR=oshima@chromium.org Review URL: https://codereview.chromium.org/467003003 Cr-Commit-Position: refs/heads/master@{#291394} git-svn-id: svn://svn.chromium.org/chrome/trunk/src@291394 0039d316-1c4b-4281-b951-d872f2087c98
-
mlamouri@chromium.org authored
The manifest_parser.{h,cc} files are colliding with new files I'm creating for the Web Manifest feature. Appcache manifest files should be prefixed by "appcache". BUG=None NOTRY=true TBR=torne (for third_party_files_whitelist.txt) Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=291388 Review URL: https://codereview.chromium.org/469413003 Cr-Commit-Position: refs/heads/master@{#291393} git-svn-id: svn://svn.chromium.org/chrome/trunk/src@291393 0039d316-1c4b-4281-b951-d872f2087c98
-
rob@robwu.nl authored
Include the stack trace of the code that triggered the error. Refactored the error generation method to prevent extension code from breaking the state of the internals. BUG=404406 Review URL: https://codereview.chromium.org/482603002 Cr-Commit-Position: refs/heads/master@{#291392} git-svn-id: svn://svn.chromium.org/chrome/trunk/src@291392 0039d316-1c4b-4281-b951-d872f2087c98
-
pauljensen@chromium.org authored
Fails check_licenses > Rename appcache/manifest_parser* to appcache/appcache_manifest_parser*. > > The manifest_parser.{h,cc} files are colliding with new files I'm > creating for the Web Manifest feature. Appcache manifest files should > be prefixed by "appcache". > > BUG=None > NOTRY=true > > Review URL: https://codereview.chromium.org/469413003 TBR=mlamouri@chromium.org Review URL: https://codereview.chromium.org/493383003 Cr-Commit-Position: refs/heads/master@{#291391} git-svn-id: svn://svn.chromium.org/chrome/trunk/src@291391 0039d316-1c4b-4281-b951-d872f2087c98
-
mkwst@chromium.org authored
This patch does three things: 1. Implements the Blink platform interface WebCredentialManagerClient by adding a CredentialManagerClient class to the password manager component. 2. Wires that implementation up to Blink's platform layer by creating an instance of the new client, held in ChromeContentRendererClient, and setting it as each new RenderView's client. 3. Stubs out IPCs for the renderer to pass messages up to the browser in order to do the heavy lifting of actually answering Blink's requests by generating and delivering Credential objects. BUG=400674 TBR=tkent@chromium.org Review URL: https://codereview.chromium.org/464883002 Cr-Commit-Position: refs/heads/master@{#291390} git-svn-id: svn://svn.chromium.org/chrome/trunk/src@291390 0039d316-1c4b-4281-b951-d872f2087c98
-
dconnelly@chromium.org authored
Screenshots available on the bug. BUG=394303 Review URL: https://codereview.chromium.org/487193003 Cr-Commit-Position: refs/heads/master@{#291389} git-svn-id: svn://svn.chromium.org/chrome/trunk/src@291389 0039d316-1c4b-4281-b951-d872f2087c98
-
mlamouri@chromium.org authored
The manifest_parser.{h,cc} files are colliding with new files I'm creating for the Web Manifest feature. Appcache manifest files should be prefixed by "appcache". BUG=None NOTRY=true Review URL: https://codereview.chromium.org/469413003 Cr-Commit-Position: refs/heads/master@{#291388} git-svn-id: svn://svn.chromium.org/chrome/trunk/src@291388 0039d316-1c4b-4281-b951-d872f2087c98
-
n.bansal@samsung.com authored
Currently setZoom() doesn't check whether zoom factor provided falls within range or not. It is possible to pass big zoom level through 'zoom' open pdf parameter which can make browser unresponsive. This patch updates the zoom factor provided in setZoom() to fall within range. BUG=303491 Review URL: https://codereview.chromium.org/475933004 Cr-Commit-Position: refs/heads/master@{#291387} git-svn-id: svn://svn.chromium.org/chrome/trunk/src@291387 0039d316-1c4b-4281-b951-d872f2087c98
-
jansson@chromium.org authored
Added warning_ function that highlights messages in orange in the debug message panel. MediaStreamTrack.onmute and MediaStreamTrack.onunmute are now highlighted in red as an error and in orange as a warning. BUG=None TEST=Manually triggered the events directly. NOTRY=TRUE Review URL: https://codereview.chromium.org/493073002 Cr-Commit-Position: refs/heads/master@{#291386} git-svn-id: svn://svn.chromium.org/chrome/trunk/src@291386 0039d316-1c4b-4281-b951-d872f2087c98
-
hirono@chromium.org authored
The class is extracted from EventRouter of Files.app. It is going to manage device states and dispatch the device events. BUG=360946, 396258 TEST=add unit tests Review URL: https://codereview.chromium.org/472603004 Cr-Commit-Position: refs/heads/master@{#291384} git-svn-id: svn://svn.chromium.org/chrome/trunk/src@291384 0039d316-1c4b-4281-b951-d872f2087c98
-
earthdok@chromium.org authored
BUG=354881 TBR=ygorshenin@chromium.org NOTRY=true Review URL: https://codereview.chromium.org/494223003 Cr-Commit-Position: refs/heads/master@{#291383} git-svn-id: svn://svn.chromium.org/chrome/trunk/src@291383 0039d316-1c4b-4281-b951-d872f2087c98
-
chrome-devtools://devtools/remote/opendgozman@chromium.org authored
BUG=370025 Review URL: https://codereview.chromium.org/489893002 Cr-Commit-Position: refs/heads/master@{#291382} git-svn-id: svn://svn.chromium.org/chrome/trunk/src@291382 0039d316-1c4b-4281-b951-d872f2087c98
-
mtomasz@chromium.org authored
Closing a file should not be abortable, since we could end up on files which once opened, are never closed. TEST=browser_tests: *FileSystemProvider*WriteFile* BUG=405821 Review URL: https://codereview.chromium.org/497673002 Cr-Commit-Position: refs/heads/master@{#291381} git-svn-id: svn://svn.chromium.org/chrome/trunk/src@291381 0039d316-1c4b-4281-b951-d872f2087c98
-
earthdok@chromium.org authored
BUG=405985 TBR=phajdan.jr@chromium.org NOTRY=true Review URL: https://codereview.chromium.org/485893009 Cr-Commit-Position: refs/heads/master@{#291380} git-svn-id: svn://svn.chromium.org/chrome/trunk/src@291380 0039d316-1c4b-4281-b951-d872f2087c98
-
chrome-admin@google.com authored
Cr-Commit-Position: refs/heads/master@{#291379} git-svn-id: svn://svn.chromium.org/chrome/trunk/src@291379 0039d316-1c4b-4281-b951-d872f2087c98
-
machenbach@chromium.org authored
TBR=yangguo@chromium.org Review URL: https://codereview.chromium.org/495313002 Cr-Commit-Position: refs/heads/master@{#291378} git-svn-id: svn://svn.chromium.org/chrome/trunk/src@291378 0039d316-1c4b-4281-b951-d872f2087c98
-
chrome-admin@google.com authored
Cr-Commit-Position: refs/heads/master@{#291377} git-svn-id: svn://svn.chromium.org/chrome/trunk/src@291377 0039d316-1c4b-4281-b951-d872f2087c98
-
blink-deps-roller@chromium.org authored
http://build.chromium.org/f/chromium/perf/dashboard/ui/changelog_blink.html?url=/trunk&range=180754:180760&mode=html TBR=wibling@chromium.org,gavinp@chromium.org BUG= Review URL: https://codereview.chromium.org/498663002 Cr-Commit-Position: refs/heads/master@{#291376} git-svn-id: svn://svn.chromium.org/chrome/trunk/src@291376 0039d316-1c4b-4281-b951-d872f2087c98
-
sanjoy.pal@samsung.com authored
BUG=406236 Review URL: https://codereview.chromium.org/485103005 Cr-Commit-Position: refs/heads/master@{#291375} git-svn-id: svn://svn.chromium.org/chrome/trunk/src@291375 0039d316-1c4b-4281-b951-d872f2087c98
-
wuchengli@chromium.org authored
- sizeimage DCHECK: The video device can adjust the buffer size to be bigger than we need as long as the data can fit. Theoretically sizeimage should be bigger than PlaneAllocationSize. But Exynos driver has a 256 byte padding for sizeimage. It is rounded up when calculating coded_size. So sizeimage can be smaller than PlaneAllocationSize. For example, say format.fmt.pix_mp.width and height are 1920x1088. format.fmt.pix_mp.plane_fmt[0].sizeimage is 2089216 (1920*1088+256). |sizeimage| is rounded up and |coded_size| becomes 1920x1089. So format.fmt.pix_mp.plane_fmt[i].sizeimage (2089216) is less than PlaneAllocationSize (1920*1090=2092800). Also, we should not round down because the coded size is passed VideoEncodeAccelerator::Client::RequireBitstreamBuffers. The client will allocate buffers according to the coded size. - bytesperline DCHECK: bytesperline of different planes should be checked against media::VideoFrame::row_bytes, not the width of coded size. BUG=387701 TEST=Run Hangout in debug builds. Review URL: https://codereview.chromium.org/406893002 Cr-Commit-Position: refs/heads/master@{#291374} git-svn-id: svn://svn.chromium.org/chrome/trunk/src@291374 0039d316-1c4b-4281-b951-d872f2087c98
-