- 20 Jun, 2014 21 commits
-
-
chrome-release@google.com authored
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@278568 0039d316-1c4b-4281-b951-d872f2087c98
-
ananta@chromium.org authored
On HiDPI windows these coordinates are in DIPs. While posting them via the PostMessage API we need to convert them back to pixel using the correct scale factor. This caused bookmarks to get incorrectly saved at times. Changes in this patch are as below:- 1. menu_controller.cc. Convert screen_loc to pixels before invoking Win32 API's as they expect values in pixels. 2. screen_win.cc. Fix the GetWindowAtScreenPoint function to convert the point to pixels before invoking the WindowFromPoint API. BUG=381605 R=sky Review URL: https://codereview.chromium.org/341763002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@278559 0039d316-1c4b-4281-b951-d872f2087c98
-
pkasting@chromium.org authored
This changes HistoryURLProviderParams from holding an ACMatches object to holding a HistoryMatches object; the HistoryMatches will no longer be fixed up in DoAutocomplete(), but rather after it returns control to the UI thread. The majority of this change is mechanical, but some nontrivial changes have to be made to DoAutocomplete() to account for how the "promote" action it could previously take must also happen on the UI thread. Therefore the |params| object also has to gain a few members to allow the post-DoAutocomplete() code to do promotion correctly. BUG=376199 TEST=none R=mpearson@chromium.org Review URL: https://codereview.chromium.org/333273009 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@278558 0039d316-1c4b-4281-b951-d872f2087c98
-
jbudorick@chromium.org authored
BUG= Review URL: https://codereview.chromium.org/342823004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@278557 0039d316-1c4b-4281-b951-d872f2087c98
-
navabi@chromium.org authored
BUG=385379,379219 R=tedchoc@chromium.org Review URL: https://codereview.chromium.org/348673003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@278556 0039d316-1c4b-4281-b951-d872f2087c98
-
amineer@chromium.org authored
Reverting on trunk per author's request to eliminate top crasher. > Win Video Capture: Add support for HDYC pixel format. > > This pixel format is a synonym of YUYV and is needed > for at least the DeckLink video capture card. > This format is not specified in Windows headers > probably because this is just a synonym of other > pixel formats, IOW they are all the same except for > the first word, which is the name read in hex > backwards: > 30323449 --> 0x30 0x32 0x34 0x49 -> 024I > 43594448 --> 0x43 0x59 0x44 0x48 -> CYDH > > and then all the YUV (422 and 420 alike) use the same > trailing sequence > ... 0x0000, 0x0010, {0x80, 0x00, 0x00, 0xaa, 0x00, 0x38, 0x9b, 0x71}} > > HDYC: http://www.fourcc.org/yuv.php#HDYC > > BUG=380939 > > Review URL: https://codereview.chromium.org/317073010 TBR=mcasas@chromium.org Review URL: https://codereview.chromium.org/345843002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@278555 0039d316-1c4b-4281-b951-d872f2087c98
-
amineer@chromium.org authored
Reverting on trunk at author's request to eliminate crasher > VideoCaptureDevice Win: Enumerate devices' supported formats when they don't have a DevicePath property. > > BUG=380939 > > Review URL: https://codereview.chromium.org/328463002 TBR=mcasas@chromium.org Review URL: https://codereview.chromium.org/340353003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@278554 0039d316-1c4b-4281-b951-d872f2087c98
-
amineer@chromium.org authored
Reverting from trunk at author's request to address crash. > Smart Revert 276260 "Win Video Capture: Add support for HDYC pixel for..." > > "Smart" because it needed some rebasing. > > > Win Video Capture: Add support for HDYC pixel format. > > > > This pixel format is a synonym of YUYV and is needed > > for at least the DeckLink video capture card. > > This format is not specified in Windows headers > > probably because this is just a synonym of other > > pixel formats, IOW they are all the same except for > > the first word, which is the name read in hex > > backwards: > > 30323449 --> 0x30 0x32 0x34 0x49 -> 024I > > 43594448 --> 0x43 0x59 0x44 0x48 -> CYDH > > > > and then all the YUV (422 and 420 alike) use the same > > trailing sequence > > ... 0x0000, 0x0010, {0x80, 0x00, 0x00, 0xaa, 0x00, 0x38, 0x9b, 0x71}} > > > > HDYC: http://www.fourcc.org/yuv.php#HDYC > > > > BUG=380939 > > > > Review URL: https://codereview.chromium.org/317073010 > > NOTRY=true > > TBR=mcasas@chromium.org > > Review URL: https://codereview.chromium.org/338853009 TBR=mcasas@chromium.org Review URL: https://codereview.chromium.org/342253002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@278553 0039d316-1c4b-4281-b951-d872f2087c98
-
binji@chromium.org authored
Doing this via HTML for now; back to RST after I/O. R=binji@chromium.org Review URL: https://codereview.chromium.org/342773003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@278552 0039d316-1c4b-4281-b951-d872f2087c98
-
byungchul@chromium.org authored
JVM's AttachCurrentThread() resets thread name if the caller doesn't pass thread name. Pass it first time call of AttachCurrentThread(). Not call next times to reduce syscall (prctl) overhead. BUG=384603 Review URL: https://codereview.chromium.org/330823004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@278551 0039d316-1c4b-4281-b951-d872f2087c98
-
davidben@chromium.org authored
They were changed in https://chromiumcodereview.appspot.com/11360211, but histograms.xml reflects the old one. BUG=none Review URL: https://codereview.chromium.org/327163003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@278550 0039d316-1c4b-4281-b951-d872f2087c98
-
cthomp@chromium.org authored
This change is related to the new plugin page action UI https://codereview.chromium.org/319553008/ BUG=307323 Review URL: https://codereview.chromium.org/300873002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@278549 0039d316-1c4b-4281-b951-d872f2087c98
-
nfullagar@google.com authored
BUG=none TEST=this is the demo R=bradnelson@chromium.org Review URL: https://codereview.chromium.org/347923002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@278548 0039d316-1c4b-4281-b951-d872f2087c98
-
nkostylev@chromium.org authored
* Don't allow launching GAIA sign in for user pod that is shown with multi-profile policy restriction * Always show policy bubble when hovering over user pod / clicking/tapping on it. BUG=385498 Review URL: https://codereview.chromium.org/341453002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@278547 0039d316-1c4b-4281-b951-d872f2087c98
-
groby@chromium.org authored
BUG=380916 Review URL: https://codereview.chromium.org/312203005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@278546 0039d316-1c4b-4281-b951-d872f2087c98
-
tfarina@chromium.org authored
This partially fixes the ozone build. Tested with: $ gn gen out/Debug_gn --args='use_ozone=true' $ ninja -C out/Debug_gn BUG=None TEST=see above TBR=brettw@chromium.org,sadrul@chromium.org NOTRY=true Review URL: https://codereview.chromium.org/338183006 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@278544 0039d316-1c4b-4281-b951-d872f2087c98
-
sbc@chromium.org authored
Add a test for this case. TEST=unit tests BUG=386220 R=binji@chromium.org, bradnelson@google.com Review URL: https://codereview.chromium.org/344833005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@278543 0039d316-1c4b-4281-b951-d872f2087c98
-
noamsml@chromium.org authored
Don't signal a service is removed unless we've signaled it was added. BUG=365835 Review URL: https://codereview.chromium.org/346873002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@278542 0039d316-1c4b-4281-b951-d872f2087c98
-
vangelis@chromium.org authored
Code cleanup for the logic that generates the labels used by the about:gpu page to report on the feature status. Also separates (and fixes) reporting for impl-side-painting and gpu rasterization. BUG=386420 Review URL: https://codereview.chromium.org/344653004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@278541 0039d316-1c4b-4281-b951-d872f2087c98
-
bengr@chromium.org authored
BUG=386593 Review URL: https://codereview.chromium.org/346833002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@278540 0039d316-1c4b-4281-b951-d872f2087c98
-
yzshen@chromium.org authored
> [Downloads] Retry renames after transient failures. > > If the cause of a rename failure is suspected of being transient > (sharing violations, suspected race conditions in the file system), then > retry the rename with an exponential backoff. > > BUG=368455 > > Review URL: https://codereview.chromium.org/319603003 TBR=asanka@chromium.org Review URL: https://codereview.chromium.org/342233002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@278537 0039d316-1c4b-4281-b951-d872f2087c98
-
- 19 Jun, 2014 19 commits
-
-
ananta@chromium.org authored
This ensures that windows created in ASH honor the shell work area etc. We have bugs today where in the first maximized window in ASH does not honor the work area leading to problems. Changes as below:- 1. Added a function IsAshProcess for Windows in ash_init.cc. This returns true if the browser is launched to serve ASH. 2. In the DefaultTargetDisplayProvider::GetTargetDisplay function check if the browser is launched for ASH along with the check for whether ASH is to be opened on startup. If yes then we get the display for the root window created for ASH. BUG=361776 R=sky Review URL: https://codereview.chromium.org/348513002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@278534 0039d316-1c4b-4281-b951-d872f2087c98
-
vmiura@chromium.org authored
Polling GL queries is taking ~7us each time on Android. Processing queries from ::DrawElements & ::DrawArrays may not be a good idea as 50 to 100 draw calls per-frame with GPU rendering is common i.e. 350~700us, and more so as we aim for handling higher draw call counts in the future. Pending queries are still polled in the following cases: - After glFlush(). - After glFinish(). - After processing any GpuCommandBufferStub IPC message. - As delayed work, at up to 1000Hz. BUG=385937 Review URL: https://codereview.chromium.org/342923002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@278533 0039d316-1c4b-4281-b951-d872f2087c98
-
nasko@chromium.org authored
BUG=357747 Review URL: https://codereview.chromium.org/310413004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@278532 0039d316-1c4b-4281-b951-d872f2087c98
-
tfarina@chromium.org authored
Now that we rolled the DEPS for speex library, we can use the GN BUILD file directory from src/third_party/speex. BUG=None TEST=gn gen out/Debug_gn && ninja -C out/Debug_gn speex TBR=brettw@chromium.org Review URL: https://codereview.chromium.org/343943003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@278531 0039d316-1c4b-4281-b951-d872f2087c98
-
rsesek@chromium.org authored
Alter the design of the bootstrap sandbox to only take over the bootstrap port of children when necessary. Rather than replacing the bootstrap port outright in the browser process, this change merely registers the sandboxed bootstrap port with launchd. When a sandboxed child is being launched with base::LaunchProcess(), a new LaunchOptions can specify a bootstrap name to look up and use as a replacement bootstrap port. The bootstrap port in the new child is replaced after fork() but before exec(). The kernel clears the IPC space during both of these system calls, so no other references to the original bootstrap port will exist after replacing the port with the sandboxed one and exec()ing. This change also partially reverts r276026, which introduced a permissive policy for NPAPI plugins. Since those plugins are no longer affected by the bootstrap sandbox, it can be removed. BUG=367863,383513,383517,383791,386330 R=jam@chromium.org, mark@chromium.org Review URL: https://codereview.chromium.org/347783002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@278530 0039d316-1c4b-4281-b951-d872f2087c98
-
zty@chromium.org authored
R=navabi@chromium.org Review URL: https://codereview.chromium.org/345793003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@278529 0039d316-1c4b-4281-b951-d872f2087c98
-
dmazzoni@chromium.org authored
This was accidentally broken in r270074 when I added support for the IAccessible2_2 interface; I got the confusing COM_INTERFACE_ENTRY syntax subtly wrong. BUG=386374 Review URL: https://codereview.chromium.org/343653005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@278528 0039d316-1c4b-4281-b951-d872f2087c98
-
jianli@chromium.org authored
This is not longer used. R=fgorski@chromium.org TBR=arv@chromium.org BUG=none TEST=tests updated Review URL: https://codereview.chromium.org/344033002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@278526 0039d316-1c4b-4281-b951-d872f2087c98
-
mukai@chromium.org authored
BUG=383015 R=xiyuan@chromium.org TEST=manually Review URL: https://codereview.chromium.org/342053003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@278525 0039d316-1c4b-4281-b951-d872f2087c98
-
baxley@chromium.org authored
PosixPlatformBackend didn't have support for detecting if an app is running. BUG=None Review URL: https://codereview.chromium.org/331843007 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@278524 0039d316-1c4b-4281-b951-d872f2087c98
-
rtenneti@chromium.org authored
contains failures due to invalid source address token client nonce and server nonce. Will add UMA histogram in chrome when this CL is merged. Send reject reason to client for debugging purposes. Protected behind new flags: FLAGS_use_early_return_when_verifying_chlo and FLAGS_send_quic_crypto_reject_reason Merge internal change: 69227401 R=jar@chromium.org, wtc@chromium.org, avd@google.com Review URL: https://codereview.chromium.org/331143006 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@278523 0039d316-1c4b-4281-b951-d872f2087c98
-
prasadv@chromium.org authored
BUG=386709 NOTRY=true Review URL: https://codereview.chromium.org/344933002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@278521 0039d316-1c4b-4281-b951-d872f2087c98
-
jonross@chromium.org authored
Revert of Reland Window Control Animations for TouchView. (https://codereview.chromium.org/316693002/) Reason for revert: In Immersice Fullscreen, when a mouse hovers near the top of the screen the header animates in. This is done by animating TopContainerView. However this view does not contain all of the title bar, and forces a paint to its canvas. With FrameCaptionButtonContainerView painting to a layer it no longer paints to the canvas of TopContainerView. Due to z-order of the views FrameCaptionButtonContainer exists below the TopContainerView as well as below the ClientView of the browser. Reverting the use of layers in M37. For M38 the use of layers can be rexamined, however changes to the header views, or how immersive mode renders, will be needed before relanding this. Original issue's description: > Reland Window Control Animations for TouchView > > The original change contained a use-after-free bug. This was caused by window crossfade animation during > maximizing, combined with input event processing. The crossfade would take the current layer and delete it. > However the next input event to the window tree would attempt to access the now deleted layer. > Original Code Review: https://codereview.chromium.org/271913002/ > Revert Review: https://codereview.chromium.org/309973002/ > Revert "Revert of Animate window control changes in TouchView (https://codereview.chromium.org/271913002/)" > This reverts commit 8863218a. > > TBR=jamescook@chromium.org > TEST=FrameCaptionButtonContainerViewTest.AnimationUpdatesLayerTree > BUG=363717 > Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=276782 TBR=jamescook@chromium.org BUG=384612, 363717 Review URL: https://codereview.chromium.org/343433009 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@278520 0039d316-1c4b-4281-b951-d872f2087c98
-
stuartmorgan@chromium.org authored
iOS 5 hasn't been supported for several releases, so this is always true. BUG=300130 Review URL: https://codereview.chromium.org/349453002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@278519 0039d316-1c4b-4281-b951-d872f2087c98
-
joaodasilva@chromium.org authored
This enables policy-for-extensions running in Public Sessions, and for extensions running as Kiosk Apps too. TBR=bartfab@chromium.org BUG=224596 Review URL: https://codereview.chromium.org/341043005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@278518 0039d316-1c4b-4281-b951-d872f2087c98
-
sievers@chromium.org authored
NOTRY=True Review URL: https://codereview.chromium.org/347893002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@278515 0039d316-1c4b-4281-b951-d872f2087c98
-
brettw@chromium.org authored
BUG= R=blundell@chromium.org Review URL: https://codereview.chromium.org/336443004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@278514 0039d316-1c4b-4281-b951-d872f2087c98
-
isherman@chromium.org authored
These are being landed in support of https://codereview.chromium.org/247223003/ BUG=329175 TEST=none TBR=phajdan.jr@chromium.org Review URL: https://codereview.chromium.org/344973002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@278513 0039d316-1c4b-4281-b951-d872f2087c98
-
elijahtaylor@chromium.org authored
This suppresses a warning about the setuid sandbox API version on Linux. BUG=385995 Review URL: https://codereview.chromium.org/335453009 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@278512 0039d316-1c4b-4281-b951-d872f2087c98
-