summaryrefslogtreecommitdiffstats
path: root/chrome/browser/browser_process_impl.h
Commit message (Collapse)AuthorAgeFilesLines
* Try 2 - Change how ui::Clipboard is accessed so there's only one per thread.erg@chromium.org2012-09-111-3/+0
| | | | | | | | | | | | | | | Currently, there can be any number of Clipboard objects, which can be massively simplified. This removes interfaces for fetching the Clipboard and makes everyone go through a single static ui::Clipboard::GetForCurrentThread() access point. [Differences from the first patch: this may fix the pdf tests, but since I have no way to run them locally or on a trybot, this is going in blind.] BUG=130805 R=jam@chromium.org TBR=tc,ben,dcheng,kaiwang First Review URL: https://chromiumcodereview.appspot.com/10911074 Review URL: https://chromiumcodereview.appspot.com/10916214 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@156027 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 155468 - Change how ui::Clipboard is accessed so there's only one per ↵dharani@google.com2012-09-091-0/+3
| | | | | | | | | | | | | | | | thread. Currently, there can be any number of Clipboard objects, which can be massively simplified. This removes interfaces for fetching the Clipboard and makes everyone go through a single static ui::Clipboard::GetForCurrentThread() access point. BUG=130805 TBR=tc (change in webkit/ is trivial) Review URL: https://chromiumcodereview.appspot.com/10911074 TBR=erg@chromium.org Review URL: https://chromiumcodereview.appspot.com/10919180 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@155615 0039d316-1c4b-4281-b951-d872f2087c98
* Change how ui::Clipboard is accessed so there's only one per thread.erg@chromium.org2012-09-071-3/+0
| | | | | | | | | | | Currently, there can be any number of Clipboard objects, which can be massively simplified. This removes interfaces for fetching the Clipboard and makes everyone go through a single static ui::Clipboard::GetForCurrentThread() access point. BUG=130805 TBR=tc (change in webkit/ is trivial) Review URL: https://chromiumcodereview.appspot.com/10911074 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@155468 0039d316-1c4b-4281-b951-d872f2087c98
* Use ChromeBrowserMainPartsAndroid.yfriedman@chromium.org2012-08-301-0/+2
| | | | | | | | | | | | | | | | | | | | | | | Includes several changes: 1) Stubs out jankometer 2) Makes some background-related profile code guarded by ENABLE_BACKGROUND 3) Remove SingletonProcess because it's guaranteed by the OS. 4) If-def out first-run code and process startup code as it's necessary handled in the Java layer on Android. In order to improve startup performance, Chrome for Android runs startup code in the java layer asynchronously with loading the native shared library. Re-using this code would result in us blocking until the entire library is loaded into memory. 5) Removes UMA code. UMA sessions are handled differently on Android as the browser isn't ever killed and is instead paused/resumed. 6) Also removes things like ManagedMode/PageCycler which are unused on Android. BUG=138184 Review URL: https://chromiumcodereview.appspot.com/10885023 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@154029 0039d316-1c4b-4281-b951-d872f2087c98
* Browser process does not try to create RemoteDebuggingServer again if it is ↵vsevik@chromium.org2012-08-241-1/+1
| | | | | | | | | | | already created anymore. BUG=143890 Review URL: https://chromiumcodereview.appspot.com/10827438 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@153275 0039d316-1c4b-4281-b951-d872f2087c98
* Move PrefMember and PrefChangeRegistrar to api directory.joi@chromium.org2012-08-211-2/+2
| | | | | | | | | | | | | | | | This is the first step in breaking Autofill's concrete dependency on prefs. These two classes are essentially utilities with very small dependencies back to PrefService (which I will break in the next change, by introducing a virtual PrefServiceBase) so they are suitable for api. TBRing other owners for mechanical changes. TBR=ben@chromium.org BUG=140037 Review URL: https://chromiumcodereview.appspot.com/10857031 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@152544 0039d316-1c4b-4281-b951-d872f2087c98
* Move ExtensionEventRouter and related into extensions namespacerdevlin.cronin@chromium.org2012-07-231-2/+2
| | | | | | | | | | | | | Moved ExtensionEventRouter, ExtensionEventRouterForwarder, ExtensionBrowserEventRouter into extensions namespace and renamed them appropriately. Also some header file gardening. BUG=137115, 117261 Review URL: https://chromiumcodereview.appspot.com/10696208 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@147984 0039d316-1c4b-4281-b951-d872f2087c98
* Remove the rest of #pragma once in one big CL.ajwong@chromium.org2012-07-111-1/+0
| | | | | | | | | For context see this thread: https://groups.google.com/a/chromium.org/forum/?fromgroups#!topic/chromium-dev/RMcVNGjB4II TBR=thakis,pkasting,jam git-svn-id: svn://svn.chromium.org/chrome/trunk/src@146163 0039d316-1c4b-4281-b951-d872f2087c98
* Put VariationsService into the chrome_variations namespace.asvitkine@chromium.org2012-07-061-2/+2
| | | | | | | | | | | | | Also, rename chrome_variations::ID to chrome_variations::VariationID, since there are other things in that namespace now (which was already the case with the protobuf classes). BUG=none TEST=compiles Review URL: https://chromiumcodereview.appspot.com/10693106 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@145608 0039d316-1c4b-4281-b951-d872f2087c98
* Remove TabCloseableStateWatcher. ChromeOS no longer needs it in the Ash world.ben@chromium.org2012-06-231-5/+0
| | | | | | | | | BUG=none TEST=none Review URL: https://chromiumcodereview.appspot.com/10666005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@143799 0039d316-1c4b-4281-b951-d872f2087c98
* Make AutocompleteClassifier a ProfileKeyedService.pkasting@chromium.org2012-06-121-1/+0
| | | | | | | | | | This also cleans up some usage of TemplateURLServiceFactory, especially in order to remove knowledge of TemplateURLService[Factory] from TestingProfile. The changes for this parallel some implementation details for the AutocompleteClassifierFactory. BUG=112557 TEST=none Review URL: https://chromiumcodereview.appspot.com/10532096 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@141580 0039d316-1c4b-4281-b951-d872f2087c98
* Fix crash in policy code caused by early shutdown.joaodasilva@chromium.org2012-05-231-3/+5
| | | | | | | | | | BUG=128328,127396 TEST=Starting chrome with --try-chrome-again=10001 doesn't crash in policy code anymore Review URL: https://chromiumcodereview.appspot.com/10388211 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@138460 0039d316-1c4b-4281-b951-d872f2087c98
* Restoring the chrome variatioons client, with a fix for browser_test ↵jwd@chromium.org2012-05-171-0/+3
| | | | | | | | | | | | | failures caused by it. The CLs that this is restoring are http://codereview.chromium.org/10343007 and http://codereview.chromium.org/10381021. BUG=121695 TEST= Review URL: https://chromiumcodereview.appspot.com/10392007 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@137662 0039d316-1c4b-4281-b951-d872f2087c98
* Taking over issue 10006037.rlp@chromium.org2012-05-141-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | | Moved WebDataService to ProfileKeyedService James: chrome\browser\ui\intents Peter: chrome\browser\ui\search_engines chrome\browser\search_engines Nicolas: chrome\browser\sync Rachel/Elliot: chrome\browser\profiles and the whole cl BUG=112234 TEST=unit-tests TBR=jhawkins@chromium.org,pkasting@chromium.org,zea@chromium.org,erg@chromium.org,isherman@chromium.org Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=136499 Review URL: https://chromiumcodereview.appspot.com/10185008 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@137014 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 136499 - Taking over issue 10006037.yusukes@google.com2012-05-111-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Moved WebDataService to ProfileKeyedService James: chrome\browser\ui\intents Peter: chrome\browser\ui\search_engines chrome\browser\search_engines Nicolas: chrome\browser\sync Rachel/Elliot: chrome\browser\profiles and the whole cl BUG=112234 TEST=unit-tests TBR=jhawkins@chromium.org,pkasting@chromium.org,zea@chromium.org,erg@chromium.org,isherman@chromium.org Review URL: https://chromiumcodereview.appspot.com/10185008 Reason of the revert: The CL broke the following linux_chromeos browser_tests. EnterpriseLoginBlocksForEnterpriseUser_0 EnterpriseLoginBlocksForEnterpriseUser_1 EnterpriseLoginBlocksForEnterpriseUser_2 EnterpriseLoginBlocksForEnterpriseUser_3 EnterpriseLoginBlocksForEnterpriseUser_4 EnterpriseLoginBlocksForEnterpriseUser_5 EnterpriseLoginDoesntBlockForNormalUser NormalLoginDoesntBlock sample log: http://build.chromium.org/p/chromium.chromiumos/builders/Linux%20ChromiumOS%20Tests%20%28dbg%29%282%29/builds/1071/steps/browser_tests/logs/stdio [14648:14648:0510/212507:358430278:FATAL:web_data_service.cc(96)] Check failed: BrowserThread::IsWellKnownThread(BrowserThread::DB). Backtrace: base::debug::StackTrace::StackTrace() [0x7ff2e9b74e76] logging::LogMessage::~LogMessage() [0x7ff2e9ba6627] WebDataService::WebDataService() [0x144d7a7] TBR=rlp@chromium.org Review URL: https://chromiumcodereview.appspot.com/10382123 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@136522 0039d316-1c4b-4281-b951-d872f2087c98
* Taking over issue 10006037.rlp@chromium.org2012-05-111-1/+0
| | | | | | | | | | | | | | | | | | | | | | | Moved WebDataService to ProfileKeyedService James: chrome\browser\ui\intents Peter: chrome\browser\ui\search_engines chrome\browser\search_engines Nicolas: chrome\browser\sync Rachel/Elliot: chrome\browser\profiles and the whole cl BUG=112234 TEST=unit-tests TBR=jhawkins@chromium.org,pkasting@chromium.org,zea@chromium.org,erg@chromium.org,isherman@chromium.org Review URL: https://chromiumcodereview.appspot.com/10185008 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@136499 0039d316-1c4b-4281-b951-d872f2087c98
* Move OOMPriorityManager and LowMemoryObserver to chrome/browser/chromeos/.thestig@chromium.org2012-05-111-2/+2
| | | | | | | | BUG=none TEST=none Review URL: https://chromiumcodereview.appspot.com/10384098 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@136485 0039d316-1c4b-4281-b951-d872f2087c98
* Make GoogleURLTracker a profile-keyed service.pkasting@chromium.org2012-05-091-3/+0
| | | | | | | | | | | | The original multi-profile work made this object use the system request context, which meant it never sent cookies to searchdomaincheck. This is bad because these are important to determining the correct domain to reply with. Instead, there should be a different instance per-profile, and these instances should use the standard Profile-scoped cookie stores, so we send the relevant google.com cookies. BUG=106086 TEST=Requests to searchdomaincheck should send cookies. Review URL: https://chromiumcodereview.appspot.com/10377054 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@135959 0039d316-1c4b-4281-b951-d872f2087c98
* Cleanup: IWYU for BrowserProcess.thestig@chromium.org2012-05-081-13/+9
| | | | | | | | BUG=none TEST=none Review URL: https://chromiumcodereview.appspot.com/10258009 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@135774 0039d316-1c4b-4281-b951-d872f2087c98
* BrowserProcessImpl owns the PolicyService, so that it can be destroyed after ↵joaodasilva@chromium.org2012-03-311-1/+3
| | | | | | | | | | | | local_state. BUG=108999 TEST=Everything works as before Review URL: http://codereview.chromium.org/9918028 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@130054 0039d316-1c4b-4281-b951-d872f2087c98
* Add enable_automation build switch.wangxianzhu@chromium.org2012-03-151-0/+2
| | | | | | | | | | | | | It's only disabled on Android to exclude automation from Android build. enable_automation=0 still doesn't work on platforms other than Android. BUG=117407 TEST=none Review URL: http://codereview.chromium.org/9696049 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@127004 0039d316-1c4b-4281-b951-d872f2087c98
* Move creation and ownership of BrowserOnlineStateObserver to content.jam@chromium.org2012-03-111-4/+0
| | | | | | | | BUG=98716 TBR=joi Review URL: https://chromiumcodereview.appspot.com/9662048 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@126084 0039d316-1c4b-4281-b951-d872f2087c98
* Hide MHTMLGenerationManager from chrome.jam@chromium.org2012-03-011-3/+0
| | | | | | | BUG=98716 Review URL: https://chromiumcodereview.appspot.com/9566001 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@124430 0039d316-1c4b-4281-b951-d872f2087c98
* Remove GetAudioManager and GetMediaStreamManager from ResourceContext. The ↵jam@chromium.org2012-02-231-3/+0
| | | | | | | | | | | reason is the content module should create all the concrete objects that it knows about, instead of depending on every embedder to do so. ResourceContext is then just the interfaces that it implements and which it provides on the IO thread. The AudioManager getter was a global, so I added a getter to the AudioManager class. MediaStreamManager now has its own static getter like other internal content classes on ResourceContext or BrowserContext. BUG=98716 Review URL: https://chromiumcodereview.appspot.com/9433006 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@123264 0039d316-1c4b-4281-b951-d872f2087c98
* Removed unused data member from chrome/browser/browser_process_impl.h.francoisk777@gmail.com2012-02-211-3/+0
| | | | | | Review URL: http://codereview.chromium.org/9416008 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@122813 0039d316-1c4b-4281-b951-d872f2087c98
* Make AudioManager non-refcounted.tommi@chromium.org2012-02-151-1/+1
| | | | | | | | | BUG=107087 TEST=media and content unit tests Review URL: https://chromiumcodereview.appspot.com/9382040 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@122102 0039d316-1c4b-4281-b951-d872f2087c98
* Add some instrumentation to BrowserProcessImpl.eroman@chromium.org2012-02-141-0/+5
| | | | | | | | | | | This tracks the callsite that releases the final module reference for BrowserProcessImpl, so it can be included in crash reports. BUG=113031 Review URL: http://codereview.chromium.org/9375037 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@121845 0039d316-1c4b-4281-b951-d872f2087c98
* Introduced the PolicyService.joaodasilva@chromium.org2012-02-091-0/+3
| | | | | | | | | | | | | | | | The PolicyService is owned by the BrowserPolicyConnector, and isn't yet used anywhere. The next step is to make the ConfigurationPolicyPrefStores get their policies from the PolicyService instead of the providers directly. The providers then can also be modified to provide both mandatory and recommended policies, and 3rd party policies. BUG=108999 TEST=All works as before; unit_tests green Review URL: http://codereview.chromium.org/9325066 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@121249 0039d316-1c4b-4281-b951-d872f2087c98
* Move creation and ownership of ResourceDispatcherHost and PluginService to ↵jam@chromium.org2012-01-111-15/+4
| | | | | | | | | | | | | | | | content. This gives a few benefits: -avoid having each embedder know when to create/destruct these objects, as well as contained objects (i.e. those related to downloads) -avoid having to tell embedders about specifics of BrowserThread startup/shutdown -move ResourceDispatcherHost's getter to content where it belongs I've taken out the DnsParallelism field trial (not used anymore, confirmed with jar) as it was the only thing that caused MetricsService to depend on IOThread initialization, which also depended on MetricsService (through FieldTrials). This two-sided dependency always annoyed me and made the code hard to restructure. BUG=98716 Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=117078 Review URL: http://codereview.chromium.org/9150016 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@117171 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 117078 - Move creation and ownership of ResourceDispatcherHost and ↵jam@chromium.org2012-01-101-4/+15
| | | | | | | | | | | | | | | | | | | PluginService to content. This gives a few benefits: -avoid having each embedder know when to create/destruct these objects, as well as contained objects (i.e. those related to downloads) -avoid having to tell embedders about specifics of BrowserThread startup/shutdown -move ResourceDispatcherHost's getter to content where it belongs Some code (extensions+promos) used the fact that RDH is NULL in unittests as a signal to not use the utility process. I've switches those unittests to set a flag on the objects instead. I've taken out the DnsParallelism field trial (not used anymore, confirmed with jar) as it was the only thing that caused MetricsService to depend on IOThread initialization, which also depended on MetricsService (through FieldTrials). This two-sided dependency always annoyed me and made the code hard to restructure. BUG=98716 Review URL: http://codereview.chromium.org/9150016 TBR=jam@chromium.org git-svn-id: svn://svn.chromium.org/chrome/trunk/src@117096 0039d316-1c4b-4281-b951-d872f2087c98
* Move creation and ownership of ResourceDispatcherHost and PluginService to ↵jam@chromium.org2012-01-101-15/+4
| | | | | | | | | | | | | | | | | content. This gives a few benefits: -avoid having each embedder know when to create/destruct these objects, as well as contained objects (i.e. those related to downloads) -avoid having to tell embedders about specifics of BrowserThread startup/shutdown -move ResourceDispatcherHost's getter to content where it belongs Some code (extensions+promos) used the fact that RDH is NULL in unittests as a signal to not use the utility process. I've switches those unittests to set a flag on the objects instead. I've taken out the DnsParallelism field trial (not used anymore, confirmed with jar) as it was the only thing that caused MetricsService to depend on IOThread initialization, which also depended on MetricsService (through FieldTrials). This two-sided dependency always annoyed me and made the code hard to restructure. BUG=98716 Review URL: http://codereview.chromium.org/9150016 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@117078 0039d316-1c4b-4281-b951-d872f2087c98
* Rip Out the Sidebar APIrdevlin.cronin@chromium.org2012-01-091-6/+1
| | | | | | | | | | | This fix removes the sidebar api and all its references from the code (primarily relating to chrome/common/extensions and chrome/browser/ui). BUG=107646 TEST=Covered by existing tests. Review URL: http://codereview.chromium.org/9006027 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@116901 0039d316-1c4b-4281-b951-d872f2087c98
* Remove the AudioManager singleton.tommi@chromium.org2011-12-121-0/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Unit tests now instantiate their own AudioManager and can choose to use the default one or provide their own mock implementation without having to worry about conflicting with the singleton. The teardown sequence of the AudioManager and its thread has been cleaned up significantly and I don't think it has been completely tested before as the audio thread was terminated before all objects that belonged to the thread had a chance to do cleanup. The AudioManager unit tests do not use the actual audio thread, so this part seems to have been left out. In Chrome, the AudioManager instance is now owned by BrowserProcessImpl and always constructed on the UI thread. This instance is then shared in the same way that several other 'manager' type objects are shared to 'content' code, via content::ResourceContext. Audio specific classes do though receive a direct pointer to the AudioManager and are required to do proper reference counting if they need to hold onto the instance. I chose to use the ResourceContext rather than direct use of g_browser_process to avoid requiring another singleton when writing relatively simple tests that touch the AudioManager. I added a couple of safeguards to guard against future regressions: - Not more than one instance of the AudioManager should be created. - The AudioManager should not be addrefed by its own thread. This can basically become a circular reference and prevent deterministic shutdown. Reviewers: Of course you're free to review everything, but here's the breakdown in terms of the bare minimum from the standpoint of "Owners approval". I'm asking Henrik to be the main reviewer of the entire patch (sorry!). Henrik: Everything minus the below, but it would be great if you could take a look at the whole thing, specifically media/audio. Pawel: I'd like you to take a generic look at this approach. The key areas as far as the singleton itself goes are in media/audio/audio_manager[_base].* and chrome/browser/browser_process*.* Satish: content/browser/speech/* media/audio/audio_manager_base.* (new reference counting code) Andrew: content/browser/renderer_host/media/* content/renderer/media/webrtc_audio_device_unittest.cc (Owner) Avi: content/browser/renderer_host/render_process_host_impl.cc content/browser/resource_context.* William: chrome/browser/profiles/profile_io_data.cc chrome/browser/browser_process*.* Robert: This is basically a heads up. I hope that I didn't break the OpenBSD implementation, but unfortunately I have no way of knowing for sure. Shijing: Please take a look at AudioManagerLinux. I replaced the set of active streams with a simple counter. BUG=105249 TEST=content_unittests, media_unittests, browser_tests. Review URL: http://codereview.chromium.org/8818012 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@114084 0039d316-1c4b-4281-b951-d872f2087c98
* This goes most of the way to re-enabling chrome_frame_net_tests by making it ↵joi@chromium.org2011-12-121-4/+0
| | | | | | | | | | | | | | a content::BrowserMainParts. The tests are still disabled until we are able to test them on IE8 and older; on IE9 all tests currently pass except for a few that hang. Additionally, this makes chrome_frame_net_tests determine protocol version using the exact same version information as npchrome_frame.dll does, so that version mismatch due to the RC dependency problems we have sometimes seen should not happen any more with this test suite. While in there, I also updated the poor_mans_trybot.bat script. BUG=105435 Review URL: http://codereview.chromium.org/8894008 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@114080 0039d316-1c4b-4281-b951-d872f2087c98
* Respect default browser policybenwells@chromium.org2011-12-121-0/+5
| | | | | | | | | | | | | | | | | | This got broken with an earlier change to perform the change to the default browser setting on the FILE thread. The file thread isn't created at the point the default browser policy is enforced, this change moves the code to later in the startup process. BUG=106610 TEST=Manual testing performed with a hacked Chromium to always set Chrome as the default regardless of local policy. QA should test with all the policy machinery setup. Linux and Mac should be tested as well. Review URL: http://codereview.chromium.org/8872047 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@113977 0039d316-1c4b-4281-b951-d872f2087c98
* Remove BrowserThread::UnsafeGetBrowserThread, add UnsafeGetMessageLoopForThread.joi@chromium.org2011-12-071-5/+0
| | | | | | | | | | | | | | This also removes several accessors on BrowserProcess that are no longer used. I wanted to remove all retrieval of MessageLoop objects via BrowserThread, but this proved harder than it looked, because several net:: classes use MessageLoop and have fairly deep assumptions that it is a real MessageLoop, e.g. they use MessageLoopForIO with its IO observers and so forth. Therefore, we now have UnsafeGetMessageLoopForThread but UnsafeGetBrowserThread is gone. TBR=abodenha@chromium.org BUG=98716 Review URL: http://codereview.chromium.org/8769013 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@113377 0039d316-1c4b-4281-b951-d872f2087c98
* Remove dead code for gpu blacklist auto-update.zmo@google.com2011-12-031-3/+0
| | | | | | | | | BUG=103851 TEST=tree R=kbr Review URL: http://codereview.chromium.org/8758003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@112879 0039d316-1c4b-4281-b951-d872f2087c98
* Remove IOThread::message_loop().joi@chromium.org2011-12-021-3/+0
| | | | | | | | | | | | | | | | | Instead introduce BrowserThread::UnsafeGetMessageLoop which is used in a couple of places. This will be removed in a follow-up change. I could have used UnsafeGetBrowserThread(id)->message_loop() but this is even easier to search for. Also, remove a couple of BrowserProcess accessors that aren't used by anybody, and that were using UnsafeGetBrowserThread. TBR=battre@chromium.org BUG=98716 Review URL: http://codereview.chromium.org/8775014 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@112697 0039d316-1c4b-4281-b951-d872f2087c98
* Have content/ create and destroy its own threads. (Re-land)joi@chromium.org2011-11-281-28/+23
| | | | | | | | | | | | | | | | | | | Change embedding API and embedders to allow for this. Push inheritance of base::Thread down to content::BrowserThreadImpl so that content::BrowserThread is just a namespace for API functions. This change temporarily disables chrome_frame_net_tests as agreed by the CF lead, see bug 105435. TBR=ben@chromium.org (IWYU change only) BUG=98716,104578,105435 Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=111695 Reverted (problems on official bot): r111698 Review URL: http://codereview.chromium.org/8477004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@111705 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 111695 - Have content/ create and destroy its own threads.joi@chromium.org2011-11-281-23/+28
| | | | | | | | | | | | | | | | | | | | | Reason: Problems on official builders. Change embedding API and embedders to allow for this. Push inheritance of base::Thread down to content::BrowserThreadImpl so that content::BrowserThread is just a namespace for API functions. This change temporarily disables chrome_frame_net_tests as agreed by the CF lead, see bug 105435. TBR=ben@chromium.org (IWYU change only) BUG=98716,104578,105435 Review URL: http://codereview.chromium.org/8477004 TBR=joi@chromium.org Review URL: http://codereview.chromium.org/8718012 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@111698 0039d316-1c4b-4281-b951-d872f2087c98
* Have content/ create and destroy its own threads.joi@chromium.org2011-11-281-28/+23
| | | | | | | | | | | | | | | | Change embedding API and embedders to allow for this. Push inheritance of base::Thread down to content::BrowserThreadImpl so that content::BrowserThread is just a namespace for API functions. This change temporarily disables chrome_frame_net_tests as agreed by the CF lead, see bug 105435. TBR=ben@chromium.org (IWYU change only) BUG=98716,104578,105435 Review URL: http://codereview.chromium.org/8477004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@111695 0039d316-1c4b-4281-b951-d872f2087c98
* DevTools: remove support for legacy remote debugger.yurys@chromium.org2011-11-241-4/+0
| | | | | | | | | | | DevTools remote debugging protocol supersedes the legacy protocol and old implementation should be removed. BUG=104625 TEST=Existing tests Review URL: http://codereview.chromium.org/8635005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@111540 0039d316-1c4b-4281-b951-d872f2087c98
* Make DevToolsManager a singleton, remove it from ContentBrowserClient.yurys@chromium.org2011-11-221-5/+0
| | | | | | | | | | | DevToolsManager should be created and destroyed inside content implementation, not by the embedder. BUG=104625 TEST=Exising tests Review URL: http://codereview.chromium.org/8609010 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@111106 0039d316-1c4b-4281-b951-d872f2087c98
* Add OVERRIDE to chrome/browser/.avi@chromium.org2011-11-211-1/+1
| | | | | | | | | BUG=104314 TEST=no change Review URL: http://codereview.chromium.org/8612007 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@110939 0039d316-1c4b-4281-b951-d872f2087c98
* Move enabling IPC logging for all child processes to the Content API.jam@chromium.org2011-11-181-13/+0
| | | | | | | BUG=98716 Review URL: http://codereview.chromium.org/8574070 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@110747 0039d316-1c4b-4281-b951-d872f2087c98
* Cleanup: Remove more forward declarations in various chrome/browser directories.thestig@chromium.org2011-11-161-2/+0
| | | | | | | | | BUG=none TEST=none Review URL: http://codereview.chromium.org/8566028 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@110367 0039d316-1c4b-4281-b951-d872f2087c98
* redesign and reimplement proxy config service and tracker, revise proxy ui ↵kuan@chromium.org2011-11-041-4/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | on cros * original plan was to revise proxy ui on cros for all proxy sources and network types, refer to bug rpt 21219 for ui details * redesign and reimplement PrefProxyConfigTracker and PrefProxyConfigService by switching the inter-dependencies between the two and renaming the latter - PrefProxyConfigService used to observe PrefProxyConfigTracker and retrieve new prefs proxy from the latter whenever the former gets notification of proxy change from prefs or delegate service to determine effective proxy config. Now, PrefProxyConfigTracker pushes new prefs proxy to the renamed ChromeProxyConfigService on the IO thread; the latter then uses it and proxy from delegate service to determine effective proxy config. - remove all thread-switching in PrefProxyConfigTracker which now lives and runs on UI thread, except for when it pushes proxy config to ChromeProxyConfigService on IO thread - enhances and moves ConfigState definition to namespace ProxyPrefs to indicate source of proxy config (policy, extension, other-precede, system, fallback) so that PrefProxyConfigTracker, ChromeProxyConfigService and chromeos::ProxyConfigServiceImpl can acccess it - extract code for deciding effective proxy config from PrefProxyConfigService into static PrefProxyConfigTracker method to be shared by all classes * re-design and re-implement chromeos::ProxyConfigServiceImpl - this now extends PrefProxyConfigTracker to act as a special of "prefs", handles all proxy changes from network and prefs notifications and uses PrefProxyConfigTracker to push effective proxy to ChromeProxyConfigService and hence to network stack - remove wrapper chromeos::ProxyConfigService - this is the authority on cros, and ChromeProxyConfigService does not have a delegat service. - provide proxy config to ui for all proxy sources: policy, extension, network or recommended (in order of precedence), also indicates if proxy is user-modifiable - handle user profile changes to use correct PrefProxyConfigTracker * modify CoreOptionsHandler and CoreChromeosOptionsHandler to implement dynamic monitoring of prefs::kProxy and on-the-fly ui changes of affected use-shared-proxies user pref * modify ui native code, html, css and javascript for internet options and proxy pages to show yellow banner with different messages (same banner as options page when there's policy), en/dis-able ui fields, set current user profile in backend * modify network dropdown menu to always show proxy settings menu item as long as there's a network * modify automation tests, PrefProxyConfigTracker and ProxyConfigSerivceImpl unittests to handle redesign, fix unittests that fail due to redesign BUG=chromium-os:20679,chromium-os:21219 TEST=verify per bugs rpts Review URL: http://codereview.chromium.org/8102019 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@108616 0039d316-1c4b-4281-b951-d872f2087c98
* Force-setting default browser through policy should not crash.benwells@chromium.org2011-11-011-0/+1
| | | | | | | | | | | | | | The call to set chrome as default browser due to policy needs to happen on the FILE thread. This change affects the call to set the default browser due to policy at startup and during runtime. BUG=101331 TEST=Manual testing performed Review URL: http://codereview.chromium.org/8409004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@108059 0039d316-1c4b-4281-b951-d872f2087c98
* Remove --no-startup-window flag when restarting chrome.atwilson@chromium.org2011-10-281-1/+1
| | | | | | | | | | | | | This fixes the problem where if chrome launches in background mode at login, the next time we restart chrome we relaunch it in background mode again. BUG=92391 TEST=Install background app, restart computer so chrome is launched on startup, go to about:flags and change a flag and choose 'Restart' - chrome should reopen any open windows on restart. Review URL: http://codereview.chromium.org/8413023 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@107763 0039d316-1c4b-4281-b951-d872f2087c98
* Flipping the order of BackgroundModeManager and StatusTray members so that ↵rlp@chromium.org2011-10-271-2/+2
| | | | | | | | | | | the StatusTray is not deleted before the BackgroundModeManager. Technically this should not be an issue, but it can occur if the NOTIFICATION_APP_TERMINATING notification is not sent. BUG=101082 TEST=passes existing, but there are no repro steps for the crash to test Review URL: http://codereview.chromium.org/8393028 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@107644 0039d316-1c4b-4281-b951-d872f2087c98
generated by cgit v1.1 at 2025-03-20 03:27:50 +0000