- 19 Feb, 2014 40 commits
-
-
rockot@chromium.org authored
Callers use ExtensionPrefs::Get instead of depending on ExtensionService for access. Where appropriate, other nearby, unnecessary references to ExtensionService have also been removed. BUG=341181 TBR=benwells@chromium.org,benjhayden@chromium.org,akalin@chromium.org,pkotwicz@chromium.org,stevenjb@chromium.org,sky@chromium.org,dbeam@chromium.org,finnur@chromium.org Review URL: https://codereview.chromium.org/156843004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251958 0039d316-1c4b-4281-b951-d872f2087c98
-
thestig@chromium.org authored
Review URL: https://codereview.chromium.org/168293002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251957 0039d316-1c4b-4281-b951-d872f2087c98
-
calamity@chromium.org authored
This CL centers the app list for Linux when the --enable-experimental-app-list-flag is on as a followup to https://codereview.chromium.org/162753002 . BUG=344442 Review URL: https://codereview.chromium.org/170183003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251956 0039d316-1c4b-4281-b951-d872f2087c98
-
thakis@chromium.org authored
r248477 made pkg-config.py print a 5-tuple. Change the default output accordingly. BUG=none R=brettw@chromium.org Review URL: https://codereview.chromium.org/171993002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251955 0039d316-1c4b-4281-b951-d872f2087c98
-
sashab@chromium.org authored
Added a list of permissions to the app info dialog, as well as the app's shortcut icon and some basic app information (name, version and description). Context menu option to open the dialog is still behind the flag --enable-app-list-app-info. BUG=266739 Review URL: https://codereview.chromium.org/146583010 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251954 0039d316-1c4b-4281-b951-d872f2087c98
-
yoshiki@chromium.org authored
BUG=342593 TEST=manually tested Review URL: https://codereview.chromium.org/165983002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251953 0039d316-1c4b-4281-b951-d872f2087c98
-
chrome://suggestionshttps://codereview.chromium.org/163953005/thestig@chromium.org authored
Reason for revert: SuggestionsCombinerTest.TestSuite and SuggestionsCombinerTest.SourcesAreNotDoneFetching crashing on Linux clang, as well as some Mac bots. Original issue's description: > The test page requires proper Canary flag to be set. See SuggestionsService::IsEnabled(). > > Details: > - Changing the interface of SuggestionsService, so results are returned via callbacks. Also updating tests. > - To support calls to SuggestionsService::FetchSuggestionsData() while data fetch takes place, we queue callbacks, and serve all data when data fetch completes. > - Adding SuggestionsService::Shutdown() to handle mid-flight shutdown. > - Making chrome://suggestions unavailable for incognito mode. > > BUG=None > Test=SuggestionsServiceTest > > Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=251935 TBR=mathp@chromium.org,beaudoin@chromium.org,jered@chromium.org,sky@chromium.org,huangs@chromium.org NOTREECHECKS=true NOTRY=true BUG=None Review URL: https://codereview.chromium.org/170743009 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251950 0039d316-1c4b-4281-b951-d872f2087c98
-
sergeyu@chromium.org authored
> Increase framerate limit in remoting host to 30fps > > BUG=344675 > R=jamiewalch@chromium.org > > Review URL: https://codereview.chromium.org/171523003 TBR=sergeyu@chromium.org Review URL: https://codereview.chromium.org/171963002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251944 0039d316-1c4b-4281-b951-d872f2087c98
-
chrome-release@google.com authored
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251942 0039d316-1c4b-4281-b951-d872f2087c98
-
rnk@chromium.org authored
TBR=hans@chromium.org NOTRY=true Review URL: https://codereview.chromium.org/171643002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251940 0039d316-1c4b-4281-b951-d872f2087c98
-
benjhayden@chromium.org authored
Reset UnloadController::is_attempting_to_close_browser_ when the download-in-progress prompt is canceled. This seems to have been broken by https://src.chromium.org/viewvc/chrome?view=rev&revision=217949 BUG=305516 Review URL: https://codereview.chromium.org/160963002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251939 0039d316-1c4b-4281-b951-d872f2087c98
-
reveman@chromium.org authored
This removes some unnecessary layers of abstraction between internal::Task and the tile manager. Prerequisite to getting rid of our large raster task objects and anonymous functions. BUG=269841 Review URL: https://codereview.chromium.org/168083002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251938 0039d316-1c4b-4281-b951-d872f2087c98
-
sergeyu@chromium.org authored
BUG=344675 R=jamiewalch@chromium.org Review URL: https://codereview.chromium.org/171523003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251937 0039d316-1c4b-4281-b951-d872f2087c98
-
noamsml@chromium.org authored
List files locally using privet. BUG=338868 Review URL: https://codereview.chromium.org/141703022 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251936 0039d316-1c4b-4281-b951-d872f2087c98
-
huangs@chromium.org authored
Details: - Changing the interface of SuggestionsService, so results are returned via callbacks. Also updating tests. - To support calls to SuggestionsService::FetchSuggestionsData() while data fetch takes place, we queue callbacks, and serve all data when data fetch completes. - Adding SuggestionsService::Shutdown() to handle mid-flight shutdown. - Making chrome://suggestions unavailable for incognito mode. BUG=None Test=SuggestionsServiceTest Review URL: https://codereview.chromium.org/163953005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251935 0039d316-1c4b-4281-b951-d872f2087c98
-
xhwang@chromium.org authored
Also updated the browser test to test the case where media pipeline starts to ask the CDM to do decryption before the session is fully loaded. BUG=344651 TEST=Updated test. R=ddorwin@chromium.org Review URL: https://codereview.chromium.org/166273009 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251934 0039d316-1c4b-4281-b951-d872f2087c98
-
achuith@chromium.org authored
BUG=344703 TEST=manual NOTRY=True Review URL: https://codereview.chromium.org/169053006 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251933 0039d316-1c4b-4281-b951-d872f2087c98
-
rockot@chromium.org authored
BUG=344079 Review URL: https://codereview.chromium.org/166903006 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251932 0039d316-1c4b-4281-b951-d872f2087c98
-
thakis@chromium.org authored
TBR=scottmg@chromium.org Review URL: https://codereview.chromium.org/162613005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251931 0039d316-1c4b-4281-b951-d872f2087c98
-
tsepez@chromium.org authored
TBR=inferno@chromium.org Review URL: https://codereview.chromium.org/171503004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251928 0039d316-1c4b-4281-b951-d872f2087c98
-
dbeam@chromium.org authored
R=estade@chromium.org BUG=281069 TEST=bug repro steps Review URL: https://codereview.chromium.org/168183002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251927 0039d316-1c4b-4281-b951-d872f2087c98
-
maniscalco@chromium.org authored
Consolidate the various implementations of SyncChangeProcessorDelegate and fake into sync/api. Replace many of the fake SyncChangeProcessor implementations with a slightly more advanced FakeSyncChangeProcessor. TBR=brettw@chromium.org BUG= Review URL: https://codereview.chromium.org/151963002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251926 0039d316-1c4b-4281-b951-d872f2087c98
-
koz@chromium.org authored
BUG=341820 Review URL: https://codereview.chromium.org/169303002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251925 0039d316-1c4b-4281-b951-d872f2087c98
-
scottmg@chromium.org authored
Previously during EndSession, a nested message loop and a task posted to the FILE thread that posted a MessageLoop::Quit were used to communicate that the FILE thread had completed outstanding writes. However, during shutdown the GPU process might be terminated before the browser has run through this code. In that case, the GPU process host might process the "lost context" and try to re-establish (synchronously) a connection with the GPU process. In this case, Windows can deny the launch of the gpu process because the window station is terminating. This results in a browser hang waiting for the GPU, which turns into a crash when the watchdog timer kills the browser. To avoid all this, use the same mechanism as Linux -- create a waitable event and simply have the FILE thread signal it (meaning it's completed previous writes). By not re-entering a UI-thread message loop, we avoid having the GPU process host messages get processed. As a side-benefit, this also means that GPU paint messages are not processed, which (I think) will avoid the ugliness of sometimes having sad tabs rendered during shutdown. This could happen because the renderers are also asynchronously killed during shutdown and so it's a race between painting the next frame and the browser window being closed. R=piman@chromium.org, cpu@chromium.org, darin@chromium.org BUG=318527,47908,142501 Review URL: https://codereview.chromium.org/170023002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251922 0039d316-1c4b-4281-b951-d872f2087c98
-
weitaosu@chromium.org authored
BUG=338952,325567 Review URL: https://codereview.chromium.org/171163003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251921 0039d316-1c4b-4281-b951-d872f2087c98
-
thakis@chromium.org authored
BUG=297672 Review URL: https://codereview.chromium.org/101463005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251920 0039d316-1c4b-4281-b951-d872f2087c98
-
gbillock@chromium.org authored
R=leng@chromium.org, markusheintz@chromium.org BUG=343234 Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=251392 Review URL: https://codereview.chromium.org/162713003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251919 0039d316-1c4b-4281-b951-d872f2087c98
-
ccameron@chromium.org authored
Code to do this was recently removed because it was no longer being used in r241225 (https://codereview.chromium.org/116103002). This is now necessary again to throttle renderers when using CoreAnimation. Frames are acked only when they are drawn. Both the CoreAnimation and the non-CoreAnimation paths are changed to behave this way. By virtue of the fact that the non-CoreAnimation path draws immediately, this should have no functional effect on that path. This differs from the mechanism deleted in the aforementioned patch in two ways. First, it uses a scoped_ptr of a struct instead of a vector of pairs to store the information about the swap being returned. This should improve readability in that the ack has struct names instead of just first and second in the pair, and in that the scoped_ptr does not suggest support for multiple pending swaps (which does not exist). Second, it does makes RWHVMac ack frames more aggressively when inside a draw call, rather than adding a call from RWHImpl to the view, to effect the ack (which is what the old way does). BUG=340133 Review URL: https://codereview.chromium.org/165703002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251918 0039d316-1c4b-4281-b951-d872f2087c98
-
pkotwicz@chromium.org authored
BUG=342316 TEST=MenuControllerMnemonicTest*.* Review URL: https://codereview.chromium.org/168033003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251917 0039d316-1c4b-4281-b951-d872f2087c98
-
jiayl@chromium.org authored
This will get rid of the 1 second delay from waiting for setInternal to fire. BUG= Review URL: https://codereview.chromium.org/171263002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251916 0039d316-1c4b-4281-b951-d872f2087c98
-
jamesr@chromium.org authored
Long ago, we used to disable compositing on chrome: and about: URLs by default since that caused a startup performance hit. We then had an --allow-webui-compositing switch to override this behavior when desired. The usefulness of this behavior has long gone and we completely ignore the behavior and the flag on aura builds. This nukes it from the code Review URL: https://codereview.chromium.org/167713003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251915 0039d316-1c4b-4281-b951-d872f2087c98
-
thestig@chromium.org authored
Review URL: https://codereview.chromium.org/170743008 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251911 0039d316-1c4b-4281-b951-d872f2087c98
-
thakis@chromium.org authored
If ANDROID_SDK_ROOT is set, it's still added to the path for now, but it's no longer passed to gyp. If you want to set a custom sdk root, call gyp like "build/gyp_chromium -Dandroid_sdk_root=path". If ANDROID_SDK_ROOT is not set, it's still getting exported with a default value that's identical to the default value of gyp's android_sdk_root variable. ANDROID_SDK_TOOLS and ANDROID_SDK_BUILD_TOOLS_VERSION are now completely ignored. Set the android_sdk_tools or android_sdk_build_tools_version gyp defines instead if you need to change either. If they are not set, envsetup no longer sets them. (Dependent on an internal that changes a bot to set these gyp defines in addition to the env vars.) BUG=330631 NOTRY=true Review URL: https://codereview.chromium.org/164193010 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251904 0039d316-1c4b-4281-b951-d872f2087c98
-
rch@chromium.org authored
that --v=1 is functional. Review URL: https://codereview.chromium.org/170743003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251903 0039d316-1c4b-4281-b951-d872f2087c98
-
vandebo@chromium.org authored
Resubmission of https://codereview.chromium.org/130263007/ with the binary resources added with dcommit. BUG=334309, 161119 TBR=oshima@chromium.org Review URL: https://codereview.chromium.org/170843002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251901 0039d316-1c4b-4281-b951-d872f2087c98
-
pkotwicz@chromium.org authored
BUG=None TEST=None Review URL: https://codereview.chromium.org/162943004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251900 0039d316-1c4b-4281-b951-d872f2087c98
-
pkotwicz@chromium.org authored
The test seems to pass fine when I run it manually on Windows Ash (including with high values of --gtest_repeat) This CL: - Makes ToplevelWindowEventHandlerTest.RunMoveLoopFailsDuringInProgressDrag look more like ToplevelWindowEventHandlerTest.Caption which I don't think is flaky on Windows Ash. - Adds an extra check which will help better understand the source of the flakiness should it occur again BUG=343167 TEST=None Review URL: https://codereview.chromium.org/168793002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251899 0039d316-1c4b-4281-b951-d872f2087c98
-
danakj@chromium.org authored
R=piman BUG= Review URL: https://codereview.chromium.org/167953003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251898 0039d316-1c4b-4281-b951-d872f2087c98
-
aurimas@chromium.org authored
BUG=326023 Review URL: https://codereview.chromium.org/167703002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251897 0039d316-1c4b-4281-b951-d872f2087c98
-
danakj@chromium.org authored
We're not planning to enable this on any new platforms, so we can just hardcode it off when not on ChromeOS. Leaving the disable flag for ChromeOS for now, as we're working on disabling that code path there. R=piman BUG= Review URL: https://codereview.chromium.org/167973003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251896 0039d316-1c4b-4281-b951-d872f2087c98
-