summaryrefslogtreecommitdiffstats
path: root/chrome/app/chrome_main_delegate.cc
Commit message (Collapse)AuthorAgeFilesLines
* Tighten up DEPS some more. NaCl/service process code are including internal ↵jam@chromium.org2012-06-041-2/+2
| | | | | | | | | content files. Fix the instances other sandbox stuff, which I'll do in a followup. BUG=98716 Review URL: https://chromiumcodereview.appspot.com/10512010 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@140346 0039d316-1c4b-4281-b951-d872f2087c98
* Add new ResourceBundle::Delegate interface.marshall@chromium.org2012-05-091-1/+1
| | | | | | | | | BUG=125351 TEST=ResourceBundle.* Review URL: https://chromiumcodereview.appspot.com/10270023 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@136039 0039d316-1c4b-4281-b951-d872f2087c98
* Make sure only the main browser process and service processes are allowed to ↵pastarmovj@chromium.org2012-05-091-2/+6
| | | | | | | | | | | | | | create the profile directory. This patch lets Chrome start with profile located on a network share on Windows Vista and newer. BUG=120388 TEST=Start Chrome with --user-data-dir pointing to a network share location and try to navigate to a web page. This should not lead to a hang of the renderer. NaCl and NPAPI plugins should run fine too. Review URL: https://chromiumcodereview.appspot.com/10390003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@136020 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 135321 - Make sure only the main browser process and service proceses ↵pastarmovj@chromium.org2012-05-041-6/+2
| | | | | | | | | | | | | | | | | | are allowed to create the profile directory. This patch lets Chrome start with profile located on a network share on Windows Vista and newer. BUG=120388 TEST=Start Chrome with --user-data-dir pointing to a network share location and try to navigate to a web page. This should not lead to a hang of the renderer. Review URL: http://codereview.chromium.org/10306009 TBR=pastarmovj@chromium.org Review URL: https://chromiumcodereview.appspot.com/10382012 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@135347 0039d316-1c4b-4281-b951-d872f2087c98
* Make sure only the main browser process and service proceses are allowed to ↵pastarmovj@chromium.org2012-05-041-2/+6
| | | | | | | | | | | | | | | create the profile directory. This patch lets Chrome start with profile located on a network share on Windows Vista and newer. BUG=120388 TEST=Start Chrome with --user-data-dir pointing to a network share location and try to navigate to a web page. This should not lead to a hang of the renderer. Review URL: http://codereview.chromium.org/10306009 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@135321 0039d316-1c4b-4281-b951-d872f2087c98
* Get chrome:// dev tool urls hooked up in content_shell.michaeln@google.com2012-04-201-11/+6
| | | | | | Review URL: https://chromiumcodereview.appspot.com/9950040 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@133107 0039d316-1c4b-4281-b951-d872f2087c98
* Fix single process mode in content_shell.jam@chromium.org2012-04-191-8/+1
| | | | | | Review URL: https://chromiumcodereview.appspot.com/10115048 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@132907 0039d316-1c4b-4281-b951-d872f2087c98
* Metro/HiDPI: Cleanup ResourceBundlesail@chromium.org2012-04-121-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | For Metro and HiDPI support we need to conditionally load resource pak files. For example, on Windows I'd like to have something like this: ..ResourceBundle::LoadCommonResources() { ....if (IsMetroMode()) { ......switch (DPIScale()) { ........case 1.0: AddDataPack("theme_resources_metro_1_0x.pak"); break; ........case 1.4: AddDataPack("theme_resources_metro_1_4x.pak"); break; ........case 1.8: AddDataPack("theme_resources_metro_1_8x.pak"); break; ......} ....} else { ......if (DPIScale() < 1.5) ........AddDataPack("theme_resources_desktop_1_0x.pak"); ......else ........AddDataPack("theme_resources_desktop_2_0x.pak"); ....} ..} As a first step this CL does the following: - create a new ResourceHandle abstract class that can be backed by a DLL on Windows. - manage all resource packs through the data_packs_ vector - clean up ResourceBundle interface by removing all the #ifdefs BUG=114311 TEST=Built and ran on Mac, Linux, Windows, Linux Arua. Review URL: http://codereview.chromium.org/10051012 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@132091 0039d316-1c4b-4281-b951-d872f2087c98
* Upstream crash changes for android.carlosvaldivia@google.com2012-04-101-1/+1
| | | | | | | | | | | | | | | | | | | | | Third time is a charm. Original Reviews: https://chromiumcodereview.appspot.com/9838033/ http://codereview.chromium.org/9967017 Revert "Revert 131593" This reverts commit e306ea7f630d4264075913ea3a1a728d98ca9605. BUG= TEST= Review URL: http://codereview.chromium.org/9960072 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@131662 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 131593erg@google.com2012-04-101-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Speculatively reverting due to gyp update error on official bots: KeyError: 'src/breakpad/breakpad.gyp:dump_syms#target while trying to load target src/remoting/remoting.gyp:remoting_linux_symbols#target' This is the only patch in the regression range that touches breakpad.gyp. --- Upstream Android native crash handling changes. This is actulaly the second time. Revert "Revert 131404 - Upstream native crash handling changes for Android." This reverts commit 421df96aab6267e963ddff16c9f738aa903a2cba. Conflicts: chrome/browser/chrome_browser_main.cc BUG= TEST= Review URL: http://codereview.chromium.org/9967017 TBR=carlosvaldivia@google.com Review URL: https://chromiumcodereview.appspot.com/10037013 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@131600 0039d316-1c4b-4281-b951-d872f2087c98
* Upstream Android native crash handling changes.carlosvaldivia@google.com2012-04-101-1/+1
| | | | | | | | | | | | | | | | | | | | This is actulaly the second time. Revert "Revert 131404 - Upstream native crash handling changes for Android." This reverts commit 421df96aab6267e963ddff16c9f738aa903a2cba. Conflicts: chrome/browser/chrome_browser_main.cc BUG= TEST= Review URL: http://codereview.chromium.org/9967017 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@131593 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 131404 - Upstream native crash handling changes for Android.msw@chromium.org2012-04-091-1/+1
| | | | | | | | | | | | | | | | | | | | Android native crash handling is almost identical to linux handling with some differences. Note that even after this change Chrome on Android will not compile with the USE_LINUX_BREAKPAD flag. Forthcomming changes in breakpad should remedy this state of affairs. BUG= TEST= Review URL: http://codereview.chromium.org/9838033 TBR=carlosvaldivia@google.com Review URL: https://chromiumcodereview.appspot.com/9999004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@131420 0039d316-1c4b-4281-b951-d872f2087c98
* Upstream native crash handling changes for Android.carlosvaldivia@google.com2012-04-091-1/+1
| | | | | | | | | | | | | | | | | Android native crash handling is almost identical to linux handling with some differences. Note that even after this change Chrome on Android will not compile with the USE_LINUX_BREAKPAD flag. Forthcomming changes in breakpad should remedy this state of affairs. BUG= TEST= Review URL: http://codereview.chromium.org/9838033 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@131404 0039d316-1c4b-4281-b951-d872f2087c98
* Remove TOOLKIT_USES_GTK and consolidate it into TOOLKIT_GTKoshima@chromium.org2012-04-051-1/+1
| | | | | | | | | | | Add gtk dependency to base.gyp for android host_os="linux" case BUG=none TEST=none Review URL: https://chromiumcodereview.appspot.com/9969080 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@130784 0039d316-1c4b-4281-b951-d872f2087c98
* Enable audio/video tag in content_shellvrk@chromium.org2012-03-071-7/+0
| | | | | | | | | | | | | | | | Some media initialization work needed to be added to the shell in order for the ffmpeg stubs to be loaded and for the media tags to be recognized. AudioManager also needed to be added to the shell, as the Chromium-equivalent lives in BrowserProcessImpl, and the media code should not assume the MediaInternals has been created. BUG=112043,116906 TEST=content_shell builds and can play the videos in the bug above Review URL: http://codereview.chromium.org/9316077 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@125442 0039d316-1c4b-4281-b951-d872f2087c98
* mac: Remove InitWebCoreSystemInterface() calls from many random places.thakis@chromium.org2012-02-141-10/+0
| | | | | | | | | | | | | | | | This is now done at the webkit api layer (https://bugs.webkit.org/show_bug.cgi?id=78246), so clients no longer have to explicitly do this. Fixes 2 TODOs, helps with the mac component build, and removes a direct WebCore dependency from client code. BUG=90078 TEST=none TBR=tony,brettw Review URL: http://codereview.chromium.org/9374020 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@121930 0039d316-1c4b-4281-b951-d872f2087c98
* Support sharing of ContentMain and BrowserMain code with embedded use cases ↵marshall@chromium.org2012-02-101-4/+1
| | | | | | | | | | | | | | | | | | | | (try #3). For the browser use case it is convenient to have a single ContentMain entry point function that handles all initialization, run and shutdown. For embedded use cases it is often necessary to integrate with existing application message loops where initialization and shutdown must be handled separately. To support sharing of this code the following changes were required: 1. Refactor the ContentMain function to create a ContentMainRunner class containing separate initialization, run and shutdown functions. 2. Refactor the BrowserMain function and BrowserMainLoop class to create a BrowserMainRunner class containing separate initialization, run and shutdown functions. 3. Add a new BrowserMainParts::GetMainMessageLoop method. This is necessary to support creation of a custom MessageLoop implementation while sharing BrowserMainRunner initialization and shutdown code. BUG=112507 TEST=none Review URL: https://chromiumcodereview.appspot.com/9375017 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@121454 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 121236 - Support sharing of ContentMain and BrowserMain code with ↵marshall@chromium.org2012-02-091-1/+4
| | | | | | | | | embedded use cases (try #2). Tests failing. Review URL: https://chromiumcodereview.appspot.com/9372027 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@121245 0039d316-1c4b-4281-b951-d872f2087c98
* Support sharing of ContentMain and BrowserMain code with embedded use cases ↵marshall@chromium.org2012-02-091-4/+1
| | | | | | | | | | | | | | | | | | | | (try #2). For the browser use case it is convenient to have a single ContentMain entry point function that handles all initialization, run and shutdown. For embedded use cases it is often necessary to integrate with existing application message loops where initialization and shutdown must be handled separately. To support sharing of this code the following changes were required: 1. Refactor the ContentMain function to create a ContentMainRunner class containing separate initialization, run and shutdown functions. 2. Refactor the BrowserMain function and BrowserMainLoop class to create a BrowserMainRunner class containing separate initialization, run and shutdown functions. 3. Add a new BrowserMainParts::GetMainMessageLoop method. This is necessary to support creation of a custom MessageLoop implementation while sharing BrowserMainRunner initialization and shutdown code. BUG=112507 TEST=none Review URL: https://chromiumcodereview.appspot.com/9347022 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@121236 0039d316-1c4b-4281-b951-d872f2087c98
* Revert "Support sharing of ContentMain and BrowserMain code with embedded ↵evan@chromium.org2012-02-061-1/+4
| | | | | | | | use cases." This reverts commit r120574. Test failures. git-svn-id: svn://svn.chromium.org/chrome/trunk/src@120581 0039d316-1c4b-4281-b951-d872f2087c98
* Support sharing of ContentMain and BrowserMain code with embedded use cases.marshall@chromium.org2012-02-061-4/+1
| | | | | | | | | | | | | | | | | | For the browser use case it is convenient to have a single ContentMain entry point function that handles all initialization, run and shutdown. For embedded use cases it is often necessary to integrate with existing application message loops where initialization and shutdown must be handled separately. To support sharing of this code the following changes were required: 1. Refactor the ContentMain function to create a ContentMainRunner class containing separate initialization, run and shutdown functions. 2. Refactor the BrowserMain function and BrowserMainLoop class to create a BrowserMainRunner class containing separate initialization, run and shutdown functions. 3. Add a new BrowserMainParts::GetMainMessageLoop method. This is necessary to support creation of a custom MessageLoop implementation while sharing BrowserMainRunner initialization and shutdown code. BUG=112507 TEST=none Review URL: https://chromiumcodereview.appspot.com/9190018 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@120574 0039d316-1c4b-4281-b951-d872f2087c98
* content: Modfiy ResourceBundle and content_shell to run with alternative pak ↵erg@chromium.org2012-01-281-1/+1
| | | | | | | | | | | | files. BUG=111326 R=jam TBR=sky,tony,ajwong,ananta Review URL: http://codereview.chromium.org/9232060 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@119566 0039d316-1c4b-4281-b951-d872f2087c98
* Suppress critical error dialogs on Windowsasanka@chromium.org2012-01-091-1/+15
| | | | | | | | | | BUG=100295 TEST=Manual. Download a file to a USB stick. Disconnect USB stick, restart Chrome and visit chrome://downloads. There should be no "There is no disk in drive..." error and the download should be marked as "Removed." Review URL: http://codereview.chromium.org/9022044 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@116897 0039d316-1c4b-4281-b951-d872f2087c98
* Added recommended pref store on Windows.joaodasilva@chromium.org2011-12-011-2/+4
| | | | | | | | | BUG=49941 TEST=Set policies for Chromium/Chrome in a registry subkey named "Recommended". Those policies become the default values and can be overridden by the user. Review URL: http://codereview.chromium.org/8551010 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@112456 0039d316-1c4b-4281-b951-d872f2087c98
* Initialize resource bundle for GPU process on Mac, so it can load its ↵jochen@chromium.org2011-11-291-0/+2
| | | | | | | | | | | | sandbox definition BUG=105720 TEST=none (guess why it broke it the first place :-/ ) Review URL: http://codereview.chromium.org/8727030 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@111992 0039d316-1c4b-4281-b951-d872f2087c98
* Load mac sandbox definitions from resources instead of the bundle.jochen@chromium.org2011-11-251-2/+9
| | | | | | | | | | | Also, move all mac sandbox unittests to content BUG=90443 TEST=content_unittests Review URL: http://codereview.chromium.org/8589001 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@111614 0039d316-1c4b-4281-b951-d872f2087c98
* Define the public interface for content browser RenderProcessHost. This ↵ananta@chromium.org2011-11-181-2/+2
| | | | | | | | | | | | | | | interface is implemented by the RenderProcessHostImpl class which lives in content\browser\renderer_host\render_process_host_impl.cc/.h. The RenderProcessHostImpl class is a consolidation of the RenderProcessHost and BrowserRenderProcessHost classes. The RenderProcessHost public interface was created from the now deleted RenderProcessHost class defined in content\browser\renderer_host\render_process_host.h. Additional methods have been added to the interface to ensure that it works correctly with the MockRenderProcessHost class used by unit tests. I had to implement a number of overrides in the MockRenderProcessHost class to ensure that tests work correctly. This was because of assumptions in the tests that the MockRPH class was a real RPH which it was till now. Added a TODO for the methods which could potentially be removed from this interface. Will revisit that in a subsequent CL. BUG=98716 TEST=No change in functionality. Hopefully it all compiles and works. Review URL: http://codereview.chromium.org/8515027 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@110615 0039d316-1c4b-4281-b951-d872f2087c98
* Allow linker initialization of lazy instancejoth@chromium.org2011-11-151-4/+4
| | | | | | | | | | | | | | Using the initializer list construct = {0} allows the object to be linker initialized. Modify the LazyInstance class design to make it a pod aggregate type that can be linker initialized this way. Also combines the instance and state members, in line with the Singleton<> class design. Introduces a new LAZY_INSTANCE_INITIALIZER macro specifically for using to init all lazy instances + modify all existing callsites to use it. (Old code would no longer compile) BUG=94925 TEST=existing tests pass. http://build.chromium.org/f/chromium/perf/linux-release/sizes/report.html?history=150&header=chrome-si&graph=chrome-si&rev=-1 should step downward. TBR=jam@chromium.org,rvargas@chromium.org,darin@chromium.org,ben@chromium.org,apatrick@chromium.org,akalin@chromium.org Review URL: http://codereview.chromium.org/8491043 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@110076 0039d316-1c4b-4281-b951-d872f2087c98
* Move content_restriction.h and main_function_params.h to ↵jam@chromium.org2011-10-311-4/+4
| | | | | | | | | content/public/common, and put them in the content namespace. BUG=98716 Review URL: http://codereview.chromium.org/8387039 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@108004 0039d316-1c4b-4281-b951-d872f2087c98
* Move ZygoteForkDelegateLinux to content/public/common.jam@chromium.org2011-10-251-2/+2
| | | | | | | BUG=98716 Review URL: http://codereview.chromium.org/8381029 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@107128 0039d316-1c4b-4281-b951-d872f2087c98
* Move content_paths.h to content/public/common.jam@chromium.org2011-10-211-1/+1
| | | | | | | | BUG=98716 TBR=avi Review URL: http://codereview.chromium.org/8375007 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@106795 0039d316-1c4b-4281-b951-d872f2087c98
* Move ContentMainDelegate to content/public/.joi@chromium.org2011-10-201-1/+1
| | | | | | | | | | | | | Mostly a trivial move since the implementation for the class (now deleted) was do-nothing and the only subclass that didn't have a full implementation was ShellMainDelegate. BUG=98716 TEST=it builds + existing tests Review URL: http://codereview.chromium.org/8356025 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@106549 0039d316-1c4b-4281-b951-d872f2087c98
* Move content_client.h into content/public.joi@chromium.org2011-10-181-1/+1
| | | | | | | | | | TBR=jam@chromium.org BUG=98716 TEST=it builds Review URL: http://codereview.chromium.org/8336007 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@106167 0039d316-1c4b-4281-b951-d872f2087c98
* Move content_switches to content\public\common.jam@chromium.org2011-10-131-1/+1
| | | | | | | BUG=98716 Review URL: http://codereview.chromium.org/8277018 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@105389 0039d316-1c4b-4281-b951-d872f2087c98
* Profiling for the renderer process.scottbyer@chromium.org2011-10-121-0/+25
| | | | | | | | | | | | | | | This lets you use --profiling-at-start=renderer and get profiler output for each renderer process started on Linux. The profiling classes are initialized at static initialization time, and the main thread is registered and the profile timer is started at that time. However, static initialization is done in the zygote, and the timer doesn't propagate across the fork, so trying to use the CPU profiler on the renderer never sampled. This patch re-registers the (new) main thread after the fork, which causes the profiler to check the state of the timer, and ends up re-starting it. A separate timer for flushing the profile and termination signal handler are added before the renderer process enters the sandbox in order to make sure the samples are written to disk. BUG=none TEST=Use it, get lovely traces, pperf away. Review URL: http://codereview.chromium.org/8083025 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@105134 0039d316-1c4b-4281-b951-d872f2087c98
* GTTF: Make browser_tests self-contained on Linux.phajdan.jr@chromium.org2011-10-061-0/+715
Windows will follow very soon, just proceeding in small steps. Previously Linux browser_tests were launching chrome binary, and Windows called PathService::Override for no reason. Mac is going to be _much_ harder. BUG=none Review URL: http://codereview.chromium.org/8178004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@104364 0039d316-1c4b-4281-b951-d872f2087c98
generated by cgit v1.1 at 2025-03-29 23:08:17 +0000