summaryrefslogtreecommitdiff
path: root/chromium/content
Commit message (Collapse)AuthorAgeFilesLines
* <chromium> Add FirstVisuallyNonEmptyLayout support for RenderViewObserverHEAD33.0.1750.170-basedSzabolcs David2014-07-312-0/+5
| | | | | | | This is needed by the implementation of loadVisuallyCommitted in the QtWebEngine. Change-Id: Ic0fcdc00f7963ea1088a1ae910bb2dbe26e9e12c Reviewed-by: Jocelyn Turcotte <jocelyn.turcotte@digia.com>
* <chromium> Use ANGLE libraries from the Qt build / installation.Michael Brüning2014-07-011-1/+10
| | | | | | | | | | | This moves libEGL and libGLESv2 from dependencies to libraries where needed. This also adds support for using the correct configuration of the ANGLE libraries for linking and runtime loading. Change-Id: I8c3a5eb11517bf03e921b257eeb3a34b7bc841ea Reviewed-by: Andras Becsi <andras.becsi@digia.com>
* <chromium> Fix Renderer and GPU threads on windowsPeter Varga2014-06-044-2/+10
| | | | | | | | | | | | | These threads are using the UI message loop on Windows per default. This won't work since the UI message loop is handled by Qt and the Renderer and GPU threads won't work with it properly. Force these threads for using the default message loop as they use it on Linux platform. Reviewed-by: Andras Becsi <andras.becsi@digia.com> Reviewed-by: Jocelyn Turcotte <jocelyn.turcotte@digia.com> Change-Id: I8b04ba9070912378cf1d13173ddff48e98f9a49b Reviewed-by: Zeno Albisser <zeno.albisser@digia.com>
* <chromium> Do not directly override libc symbols from the library.Zeno Albisser2014-06-041-14/+0
| | | | | | | | | Instead we export _override symbols and add the symbol renaming directly into the QtWebEngineProcess source. Reviewed-by: Andras Becsi <andras.becsi@digia.com> Change-Id: I15049609dd77be6de2a2398f25a37fff1b6f5519 Reviewed-by: Zeno Albisser <zeno.albisser@digia.com>
* <chromium> fixup select elements.Pierre Rossi2014-06-042-3/+3
| | | | | | | | | | | We use RenderWidgetHostViewQt, not RWHVMac, even on Mac. Since some platform decisions seem to have transpired all the way to the content layer, we should simply use the web ui for select elements on mac for the time being. Reviewed-by: Jocelyn Turcotte <jocelyn.turcotte@digia.com> Change-Id: Ib430f8686862cf0958ccdbfefb8bfa36af590e97 Reviewed-by: Zeno Albisser <zeno.albisser@digia.com>
* <chromium> Get rid of the gtk/pango/cairo dependencyAndras Becsi2014-06-042-2/+2
| | | | | | | | This also removes the aura dependency to chrome resources since we repack the needed resources ourselves. Reviewed-by: Zeno Albisser <zeno.albisser@digia.com> Change-Id: I0368bb36948ba9612040ed869ef818d4b8471b9b
* <chromium> Remove the Running without renderer sandbox error messageJocelyn Turcotte2014-06-041-1/+0
| | | | | | | | | We are currently not planing to enable the sandbox and the error pollutes the auto tests output. Reviewed-by: Andras Becsi <andras.becsi@digia.com> Change-Id: I2675aa2e03394f1c03e4df6bd1b21764ed19206a Reviewed-by: Zeno Albisser <zeno.albisser@digia.com>
* <chromium> Blacklist the skypebuttons pluginJocelyn Turcotte2014-06-041-0/+1
| | | | | | | | | | | | | | | Even though plugins are disabled it happens that the libraries are loaded and cause a crash since skypebuttons pulls Qt4 with it on Linux and creates a dynamic linking error conflicting with Qt5 symbols. Add the plugin library name to the blacklist to avoid it being loaded altogether. We have a similar fix in QtWebKit doing the same thing. Reviewed-by: Andras Becsi <andras.becsi@digia.com> Change-Id: I45abf31c4e94a8b61aff85765a91436dabae1b2e Reviewed-by: Zeno Albisser <zeno.albisser@digia.com>
* <chromium> Add seams to setup GL contexts sharing with QtQuick.Jocelyn Turcotte2014-06-042-1/+12
| | | | | | | | | This will allow us to know right before the first GL context is instantiated by Chromium so that we can install those contexts to be shared with QtQuick GL contexts as well. Change-Id: Id55337a7b42d25ac084698a23dbfab06cb273505 Reviewed-by: Zeno Albisser <zeno.albisser@digia.com>
* <chromium> Add accessors for the Qt delegated renderer integration.Jocelyn Turcotte2014-06-043-0/+14
| | | | | | | | This is needed to fetch the MessageLoop, the MailboxManager and the SyncPointManager of the GPU in-process host. Change-Id: I7f38e32b2df11da5b046f16643841d34260c11fb Reviewed-by: Zeno Albisser <zeno.albisser@digia.com>
* <chromium> Fix the build with a GL ES2 configured Qt.Jocelyn Turcotte2014-06-041-0/+1
| | | | | | | | | | | | | | | | | | | | GLES/gl2.h is included through Qt public headers and the copy of Chromium is used since its include path comes before /usr/include. The problem is that this header is incompatible for some reasons, one of them being that it converts all GL function symbols from gl* to GLES2*. Qt layer code should always need to go through GL directly, so make sure that only GYP targets that depend directly on gpu.gyp, khronos.gyp or webkit_gpu.gyp will have an include path pointing to those headers. Replace all_dependent_settings with direct_dependent_settings and control which target inherits this include_dirs from its dependencies by using export_dependent_settings. Change-Id: I82ae8a5a62f7d968375b971757b2126670a02461 Reviewed-by: Zeno Albisser <zeno.albisser@digia.com>
* <chromium> Solve conflicts when including both QtOpenGL headers and ↵Jocelyn Turcotte2014-06-041-0/+1
| | | | | | | | | | resource_provider.h If resource_provider.h is going to be used to integrate delegated frame to external compositors, it should avoid conflicting with the system's gl.h. Change-Id: Ie37d6cde263157e6717cc006a0896f0b9ebdaa5d Reviewed-by: Zeno Albisser <zeno.albisser@digia.com>
* <chromium> Build files necessary for touch and gestures.Jocelyn Turcotte2014-06-041-1/+1
| | | | | | | | Also guard the use of MessagePumpAuraX11 in events_x.cc. We need to build it to get symbols depending on base::NativeEvent. Change-Id: Ib7bb4fb1fc8692df1b8151c3d159de3d0f73076f Reviewed-by: Zeno Albisser <zeno.albisser@digia.com>
* <chromium> Do not modify the child path.Zeno Albisser2014-06-041-1/+1
| | | | | | | | | | We currently only have a single process binary for Qt. Therefore we should not choose a different binary based on required privileges. However, this patch can only be a preliminary solution. May be we should instead implement our own ChildProcessHost. Change-Id: I03af6257c7be04ab09c9828d707d30430961a17c Reviewed-by: Zeno Albisser <zeno.albisser@digia.com>
* Update Chromium snapshot to stable version 33.0.1750.170Andras Becsi2014-06-0435-185/+238
| | | | | | | | | | | | | | | This is meant as a baseline commit hence it does not include the patches we need to apply for QtWebEngine. All patches should be rebased on top of this commit so we can get rid of the external patches directory. In future these baseline commits always have to include the exact Chromium version returned by version_resolver.py's currentVersion() in their first line, so that we can retrieve the patches on top to apply on the upstream repository. This also includes a ninja update. Change-Id: I60abeadb785a3b7d149c58b65ddb5a823fed3083 Reviewed-by: Jocelyn Turcotte <jocelyn.turcotte@digia.com>
* Fix Renderer and GPU threads on windowsPeter Varga2014-05-163-1/+9
| | | | | | | | | | | | These threads are using the UI message loop on Windows per default. This won't work since the UI message loop is handled by Qt and the Renderer and GPU threads won't work with it properly. Force these threads for using the default message loop as they use it on Linux platform. Change-Id: Ie3582583e5d1644faa2875e015a0908ba148d91f Reviewed-by: Andras Becsi <andras.becsi@digia.com> Reviewed-by: Jocelyn Turcotte <jocelyn.turcotte@digia.com>
* Fix chrome_FileThread crash on windowsPeter Varga2014-05-141-1/+1
| | | | | | | | | The file thread won't do anyting if it uses the Qt event loop therefore it won't quit properly and this behavior leads to a crash. Thus the chromium's IO message loop should be used on Windows too. Change-Id: Ieea0ceb8bd732ed6c9ca172620511d78b0a5d95c Reviewed-by: Andras Becsi <andras.becsi@digia.com>
* Do not directly override libc symbols from the library.Zeno Albisser2014-04-231-14/+0
| | | | | | | | Instead we export _override symbols and add the symbol renaming directly into the QtWebEngineProcess source. Change-Id: I209a7dcf42772bb993e966f253dd2d1c7013dceb Reviewed-by: Andras Becsi <andras.becsi@digia.com>
* [Mac] fixup select elements.Pierre Rossi2014-04-092-3/+3
| | | | | | | | | | We use RenderWidgetHostViewQt, not RWHVMac, even on Mac. Since some platform decisions seem to have transpired all the way to the content layer, we should simply use the web ui for select elements on mac for the time being. Change-Id: Iefe1dd3b246fc210ac18ff9eb0e7ad498c061eac Reviewed-by: Jocelyn Turcotte <jocelyn.turcotte@digia.com>
* Get rid of the gtk/pango/cairo dependencyAndras Becsi2014-03-252-2/+2
| | | | | | | | This also removes the aura dependency to chrome resources since we repack the needed resources ourselves. Change-Id: I8180d5668334540cfd88ade449f3f0c966b989ce Reviewed-by: Zeno Albisser <zeno.albisser@digia.com>
* Update to new stable branch 1750Andras Becsi2014-03-202160-61618/+101647
| | | | | | | | | This also includes an updated ninja and chromium dependencies needed on Windows. Change-Id: Icd597d80ed3fa4425933c9f1334c3c2e31291c42 Reviewed-by: Zoltan Arvai <zarvai@inf.u-szeged.hu> Reviewed-by: Zeno Albisser <zeno.albisser@digia.com>
* Remove the Running without renderer sandbox error messageJocelyn Turcotte2014-02-131-1/+0
| | | | | | | | We are currently not planing to enable the sandbox and the error pollutes the auto tests output. Change-Id: Idd2e7eeea8f890f55dd6b6d513a7a43890e7d5b4 Reviewed-by: Andras Becsi <andras.becsi@digia.com>
* Blacklist the skypebuttons pluginJocelyn Turcotte2014-02-131-0/+1
| | | | | | | | | | | | | | Even though plugins are disabled it happens that the libraries are loaded and cause a crash since skypebuttons pulls Qt4 with it on Linux and creates a dynamic linking error conflicting with Qt5 symbols. Add the plugin library name to the blacklist to avoid it being loaded altogether. We have a similar fix in QtWebKit doing the same thing. Change-Id: I6706d45d1f19252d3b60af7b97c0a3a729dfe8b7 Reviewed-by: Andras Becsi <andras.becsi@digia.com>
* [Backport] InstantExtended: Send search URLs to renderers.jered@chromium.org2014-02-125-1/+95
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Previously, navigations initiated by an instant renderer were bounced to the browser to be rebucketed into an instant or non-instant renderer. But navigations from non-instant renderers to instant URLs (i.e. privileged search page URLs) were not rebucketed, because the renderer had no knowledge of which URLs were instant URLs, and it would be too expensive to bounce ALL URLs. As a result, non-instant pages like google.com/setprefs could not redirect to instant pages like google.com/search. This change has InstantService tell renderers about URLs associated with the default search engine, and uses this knowledge to bounce renderer-initiated navigations to likely instant URLs from non-instant processes back into the browser for rebucketing. So now link clicks from non-instant pages to instant pages will put the destination pages into an instant process. Unfortunately, though, redirects are still broken. For example, 0. User clicks "Set preferences" button on an instant page. 1. Instant renderer bounces google.com/setprefs to the browser. 2. Browser says google.com/setprefs is not an instant URL, and assigns it to a non-instant renderer. 3. After rebucketing to the non-instant renderer, google.com/setprefs is marked as a browser initiated request(!) 4. /setprefs redirects to /search, which _is_ an instant URL, but because /setprefs is marked as browser initiated the non-instant renderer does not get a chance to bounce it back to the browser. I tried working around this by giving redirects a chance to bounce back to the browser in step #4, but this broke the signin process model in a scary way that I don't fully understand. It seems like the right fix here is going to need to EITHER follow the redirect chain in step #2 when determining if an URL is an instant URL, OR somehow flag the bounced redirect request for further inspection in step #3. This change also includes a small side benefit. Since renderers now know about instant URLs, we can suppress a flash of a baked-in error page in the event of an error while loading the InstantExtended new tab page. TEST=manual,unit,browsertest BUG=271088,223754 Review URL: https://codereview.chromium.org/23455047 Change-Id: I8a552e7d51d480c09efbfe77f5a2786f56d471ad git-svn-id: svn://svn.chromium.org/chrome/trunk/src@226103 0039d316-1c4b-4281-b951-d872f2087c98 Reviewed-by: Andras Becsi <andras.becsi@digia.com>
* Update snapshot with updated patchesAndras Becsi2013-12-173-19/+14
| | | | | | | | | | | | Mountain Lion's clang does not support incomplete types in templates so remove some new forward declarations. This also removes a patch with an unneded export that we used when a separate library needed the symbol. This diff was automatically created with take_snapshot.py. Change-Id: Ie960fa23aee531cb5fc1677b8e77fceab7dce1b0 Reviewed-by: Jocelyn Turcotte <jocelyn.turcotte@digia.com>
* Update Chromium to branch 1650 (31.0.1650.63)Andras Becsi2013-12-131515-55999/+44982
| | | | | Change-Id: I57d8c832eaec1eb2364e0a8e7352a6dd354db99f Reviewed-by: Jocelyn Turcotte <jocelyn.turcotte@digia.com>
* Update chromium to branch 1599.Zeno Albisser2013-11-29205-3966/+2221
| | | | | Change-Id: I04e775a946a208bb4500d3b722bcb05c82b9d7cb Reviewed-by: Andras Becsi <andras.becsi@digia.com>
* Add seams to setup GL contexts sharing with QtQuick.Jocelyn Turcotte2013-11-062-1/+12
| | | | | | | | | This will allow us to know right before the first GL context is instantiated by Chromium so that we can install those contexts to be shared with QtQuick GL contexts as well. Change-Id: Ia2de987edb5a87097c2b29bedd8a1f908141d8ee Reviewed-by: Zeno Albisser <zeno.albisser@digia.com>
* Add accessors for the Qt delegated renderer integration.Jocelyn Turcotte2013-11-063-0/+14
| | | | | | | | This is needed to fetch the MessageLoop, the MailboxManager and the SyncPointManager of the GPU in-process host. Change-Id: Ide000254dc8525e00388df8fd182f77405f8451c Reviewed-by: Zeno Albisser <zeno.albisser@digia.com>
* Fix the build after the GL ES2 fix.Jocelyn Turcotte2013-11-011-0/+1
| | | | | | | The patch was incomplete and didn't survive a clean build. Change-Id: I86a5bc13755c0d028d53146eb1d0d708bf429dd9 Reviewed-by: Jocelyn Turcotte <jocelyn.turcotte@digia.com>
* Do not forward declare UIResourceRequest, Identity and IdentityKey.Zeno Albisser2013-10-292-40/+39
| | | | | | | | | | Clang / libc++ does not support incomplete types in templates. See: http://clang.llvm.org/compatibility.html#undep_incomplete This patch will be squashed into the next chromium update. Change-Id: I46131d53494007548444bc4d158c2208a012ece4 Reviewed-by: Andras Becsi <andras.becsi@digia.com>
* Initial import.Zeno Albisser2013-08-153171-0/+575052