- 04 Dec, 2012 36 commits
-
-
tzik@chromium.org authored
- This CL changes the directory title for origins, from "chrome-extension://exampleextension" to "exampleextension" - Also, drops file name escape. BUG=163554 Review URL: https://codereview.chromium.org/11411280 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@170887 0039d316-1c4b-4281-b951-d872f2087c98
-
kinuko@chromium.org authored
- The method takes FileSystemURL and returns a new enum: fileapi::SyncFileStatus, which takes one of either: UNKNOWN, SYNCED, HAS_PENDING_CHANGES or CONFLICTING BUG=163860 TEST=SyncFileSystemService.GetFileSyncStatus Review URL: https://codereview.chromium.org/11421197 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@170886 0039d316-1c4b-4281-b951-d872f2087c98
-
danakj@chromium.org authored
BUG=163454 R=sky Depends on: https://codereview.chromium.org/11280251/ NOTRY=true Review URL: https://chromiumcodereview.appspot.com/11414251 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@170885 0039d316-1c4b-4281-b951-d872f2087c98
-
mazda@chromium.org authored
BUG=153703 Review URL: https://codereview.chromium.org/11419274 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@170884 0039d316-1c4b-4281-b951-d872f2087c98
-
glider@google.com authored
BUG=127536 Review URL: https://codereview.chromium.org/11434097 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@170883 0039d316-1c4b-4281-b951-d872f2087c98
-
scottmg@google.com authored
Move print_preview_test because it's only used in unit_tests, and update as-a-result unneeded dependency on test_shell_test_support. R=jam@chromium.org TEST=interactive_ui_tests, unit_tests, and browser_tests link Review URL: https://codereview.chromium.org/11434098 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@170882 0039d316-1c4b-4281-b951-d872f2087c98
-
jamesr@chromium.org authored
We only have to run the complete tree synchronization algorithm if the cc::Layer tree's structure is actually changed, otherwise we can just push properties over since the cc::LayerImpl tree structure is never changed outside of commit. Since scroll offset updates are tied into the tree synchronization algorithm, we currently have to do a full tree sync for scroll updates. Fixing this will speed up scroll operations but requires a bit more work. Speeds up cc_perftests tenTenSingleThread by 7.3% BUG=161166 Review URL: https://chromiumcodereview.appspot.com/11316297 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@170881 0039d316-1c4b-4281-b951-d872f2087c98
-
akalin@chromium.org authored
This is a retry of r169875, hopefully with fewer regressions. This time, I simply notify the theme service (instantiating it if necessary) when a theme extension is installed. This should avoid the theme regression since that path is not taken on browser startup. BUG=161203 TBR=pkotwicz@chromium.org Review URL: https://codereview.chromium.org/11411330 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@170880 0039d316-1c4b-4281-b951-d872f2087c98
-
danakj@chromium.org authored
This covers remaining content/ and webkit/ manual ref-counting. BUG=163454 R=piman Depends on: https://codereview.chromium.org/11418217/ NOTRY=true Review URL: https://chromiumcodereview.appspot.com/11428099 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@170879 0039d316-1c4b-4281-b951-d872f2087c98
-
danakj@chromium.org authored
R=vandebo@chromium.org BUG=163454 Depends on: https://codereview.chromium.org/11428099/ NOTRY=true Review URL: https://chromiumcodereview.appspot.com/11316263 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@170878 0039d316-1c4b-4281-b951-d872f2087c98
-
danakj@chromium.org authored
Instead of giving const pointers to the renderer, we should provide it with non-const pointers, and expect it to consume the render passes that we provide it. In ubercomp, the delegating renderer will pass ownership of the passes to the CompositorFrame. Covered by existing tests, no change in behaviour. BUG=152337 R=enne,piman NOTRY=true Review URL: https://chromiumcodereview.appspot.com/11419269 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@170877 0039d316-1c4b-4281-b951-d872f2087c98
-
tzik@chromium.org authored
TEST=existing test, GDataWapiParserTest.* BUG= Review URL: https://chromiumcodereview.appspot.com/11428046 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@170876 0039d316-1c4b-4281-b951-d872f2087c98
-
derat@chromium.org authored
This removes the code for sending the user to GView for PDF and .ppt files. The --enable-gview flag has been passed unconditionally on Chrome OS for a long time, but we ignore it in official builds. For Chromium OS, I believe that https://chrome.google.com/webstore/detail/docs-pdfpowerpoint-viewer/nnbmlagghjjcbdhgmkedmbmedengocbn provides similar functionality. BUG=161786 TBR=ben@chromium.org Review URL: https://chromiumcodereview.appspot.com/11411071 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@170875 0039d316-1c4b-4281-b951-d872f2087c98
-
oshima@chromium.org authored
rename files to match IDR names. BUG=152929 TEST=none Review URL: https://codereview.chromium.org/11348366 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@170872 0039d316-1c4b-4281-b951-d872f2087c98
-
dalecurtis@google.com authored
XP seems to be lowering the priority of the thread responding to audio callbacks when backgrounded, causing glitching. BUG=161307 TEST=background playback on XP works without issue. Review URL: https://codereview.chromium.org/11316284 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@170870 0039d316-1c4b-4281-b951-d872f2087c98
-
mpearson@chromium.org authored
Tweaks HQP "new scoring" by (1) By a smooth squash, prevent HQP from scoring above 1400. This makes sure inlineable, high-quality, prefix matches (whether scored by HUP or by the HUP-like mode in HQP), which has scores in the 1400-1410 range, are not trumped. (2) Remove any credit for mid-word matches in titles. I decided spacing in titles should always make sense and allowing mid-word matches here seems wrong. Also, I changed the name of the "new scoring" field trial as well so we can distinguish the new behavior trial from the old behavior trial. This trial is set up independent of the "old scoring" ignore-all-mid-word-matches field trial. I prefer it this way because then I can easily enable or disable one without having to change much code. Will analyze them in a dependent/correlated fashion--that is, I will only look at this trial when in the control group of the ignore-mid-word-matches trial and will only analyze the mid-word-matches trial when in the control group of this trial. BUG=161911 TEST= Review URL: https://chromiumcodereview.appspot.com/11416285 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@170869 0039d316-1c4b-4281-b951-d872f2087c98
-
jamesr@chromium.org authored
There's a measurable (2.3-3%) perf improvement from inlining QuadF's dtor and ctor, even though FindBadConstructs thinks it's too large. BUG= NOTRY=true Review URL: https://chromiumcodereview.appspot.com/11280279 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@170868 0039d316-1c4b-4281-b951-d872f2087c98
-
fsamuel@chromium.org authored
> Browser Plugin: Update DOM Node attributes when properties are updated > > BUG=163611 > Test=BrowserPluginHostTest.*, BrowserPluginTest.*, WebViewTest.* > > Review URL: https://codereview.chromium.org/11418261 TBR=fsamuel@chromium.org Review URL: https://codereview.chromium.org/11415279 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@170867 0039d316-1c4b-4281-b951-d872f2087c98
-
fsamuel@chromium.org authored
BUG=163611 Test=BrowserPluginHostTest.*, BrowserPluginTest.*, WebViewTest.* Review URL: https://codereview.chromium.org/11418261 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@170866 0039d316-1c4b-4281-b951-d872f2087c98
-
csharp@chromium.org authored
This will hide the popup when the browser changes size or location. Also add some tests for the WidgetObserver for the function we are observing with. Resubmitting https://codereview.chromium.org/11308124/ with CloseWidgetAndNoLeaking disable on aura TBR=sky@chromium.org BUG= Review URL: https://chromiumcodereview.appspot.com/11414266 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@170864 0039d316-1c4b-4281-b951-d872f2087c98
-
chrome-admin@google.com authored
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@170863 0039d316-1c4b-4281-b951-d872f2087c98
-
ulan@chromium.org authored
R=jkummerow@chromium.org Review URL: https://chromiumcodereview.appspot.com/11418290 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@170862 0039d316-1c4b-4281-b951-d872f2087c98
-
chrisgao@chromium.org authored
NOTRY=true BUG=none Review URL: https://chromiumcodereview.appspot.com/11414267 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@170861 0039d316-1c4b-4281-b951-d872f2087c98
-
tedchoc@chromium.org authored
This value used to be defined on the window object, but has since moved to the "client". BUG=163004 Review URL: https://chromiumcodereview.appspot.com/11348336 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@170860 0039d316-1c4b-4281-b951-d872f2087c98
-
fsamuel@chromium.org authored
Review URL: https://codereview.chromium.org/11299295 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@170859 0039d316-1c4b-4281-b951-d872f2087c98
-
tonyg@chromium.org authored
BUG=163680 TEST=Local on android Review URL: https://codereview.chromium.org/11299314 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@170858 0039d316-1c4b-4281-b951-d872f2087c98
-
rjkroege@chromium.org authored
BUG=157656 Review URL: https://chromiumcodereview.appspot.com/11280255 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@170857 0039d316-1c4b-4281-b951-d872f2087c98
-
danakj@chromium.org authored
BUG=163984 R=derat@chromium.org NOTRY=true Review URL: https://codereview.chromium.org/11421213 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@170856 0039d316-1c4b-4281-b951-d872f2087c98
-
mseaborn@chromium.org authored
These days, Linux Chromium uses two sandboxes simultaneously: a SUID sandbox and (on recent kernels) a seccomp-BPF sandbox. There's no reason to disable the seccomp-BPF sandbox when running NaCl tests. There's not much reason to disable the SUID sandbox either: the SUID helper should be installed on the bots these days, but if it's not present Chromium should continue fine without it. BUG=none TEST=nacl_integration Review URL: https://codereview.chromium.org/11412294 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@170855 0039d316-1c4b-4281-b951-d872f2087c98
-
danakj@chromium.org authored
R=piman,enne BUG=152337 NOTRY=true Review URL: https://chromiumcodereview.appspot.com/11419296 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@170854 0039d316-1c4b-4281-b951-d872f2087c98
-
danakj@chromium.org authored
Tests: content_unittests:CCMessagesTest.AllQuads content_unittests:CCMessagesTest.Resources BUG=152337 R=piman NOTRY=true Review URL: https://chromiumcodereview.appspot.com/11308306 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@170853 0039d316-1c4b-4281-b951-d872f2087c98
-
wtc@chromium.org authored
of HMAC::Init() and HMAC::Sign(). R=agl@chromium.org,bradnelson@chromium.org,thakis@chromium.org BUG=none TEST=none Review URL: https://chromiumcodereview.appspot.com/11419270 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@170852 0039d316-1c4b-4281-b951-d872f2087c98
-
danakj@chromium.org authored
This class behaves like scoped_refptr and wraps the raw SkRefCnt subclass so that we don't have to call ref() and unref() directly on the pointers. Tested by: unit_tests:RefPtrTest.ReferenceCounting unit_tests:RefPtrTest.Construct unit_tests:RefPtrTest.DeclareAndAssign unit_tests:RefPtrTest.Assign unit_tests:RefPtrTest.Upcast BUG=163454 NOTRY=true Review URL: https://chromiumcodereview.appspot.com/11418217 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@170851 0039d316-1c4b-4281-b951-d872f2087c98
-
rtenneti@chromium.org authored
Revert 170800 - Speculatively reverting 166585 to see if it fixes issue 160300 - 6% startup regression on Mac 10.6 Revert 166585 - Add a histogram enum to determine the cat's flavor and how many bits there are in it. BUG=159886, 160300 Review URL: https://codereview.chromium.org/11391002 TBR=mark@chromium.org Review URL: https://codereview.chromium.org/11348360 TBR=mark@chromium.org Review URL: https://codereview.chromium.org/11411343 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@170850 0039d316-1c4b-4281-b951-d872f2087c98
-
boliu@chromium.org authored
by making timeout from 5 (default) to 15 seconds. BUG=152033 Android java test change. Ran through android trybot NOTRY=true Review URL: https://chromiumcodereview.appspot.com/11316304 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@170848 0039d316-1c4b-4281-b951-d872f2087c98
-
danakj@chromium.org authored
NOTRY=true R=yusukes@chromium.org BUG=162268 Depends on: https://codereview.chromium.org/11421055/ Depends on: https://codereview.chromium.org/11417144/ Depends on: https://codereview.chromium.org/11415124/ Review URL: https://chromiumcodereview.appspot.com/11280153 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@170847 0039d316-1c4b-4281-b951-d872f2087c98
-
- 03 Dec, 2012 4 commits
-
-
benwells@chromium.org authored
There will be system tray support for these coming out in future. In the meantime we don't want apps to start relying on the background mode. BUG=163770 Review URL: https://chromiumcodereview.appspot.com/11421193 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@170844 0039d316-1c4b-4281-b951-d872f2087c98
-
satorux@chromium.org authored
These functions are not used. We can add them back if needed. Less code to maintain is preferable. BUG=none TEST=none Review URL: https://codereview.chromium.org/11419283 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@170843 0039d316-1c4b-4281-b951-d872f2087c98
-
benwells@chromium.org authored
This function is not used anywhere and has been superceded by the CalculateKMeanColor functions in color_analysis. BUG=None Review URL: https://chromiumcodereview.appspot.com/11418280 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@170842 0039d316-1c4b-4281-b951-d872f2087c98
-
brettw@chromium.org authored
This makes Graphics2D resource creation no longer under the "dev" flag. It also makes binding a graphics context non-synchronous. It doesn't need to be synchronous other than returning success/failure, which almost nobody will check anyway, and most success/failure cases we can detect in the proxy anyway. Doing this prevents the synchronous bind from racing with the async creation in the nested-message-loop case which can run sync messages out-of-order. BUG= Review URL: https://codereview.chromium.org/11308332 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@170841 0039d316-1c4b-4281-b951-d872f2087c98
-