summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
...
* Remove QWebEngineViewPrivate::m_pendingContextMenuEventJoerg Bornemann2017-09-113-6/+1
| | | | | | | | | | | | | | | | | | | | | This flag was set in QWebEngineView::contextMenuEvent and checked in QWebEnginePage::contextMenuRequested. The latter would bail out if the flag was not set. When the user pressed Shift-F10, the key event was received by RenderWidgetHostViewQtDelegateWidget::event and forwarded to Chromium. Blink's default event handler invoked the context menu, and our callback QWebEnginePage::contextMenuRequested was called. But nothing happened, because m_pendingContextMenuEvent has never been set. There is no reason to have this flag. React on every context menu request just like in the QtQuick implementation. Now pressing Shift-F10 invokes the context menu on web pages. Task-number: QTBUG-58306 Change-Id: I2db1b17604e5521e44613297120a964cc4e4d544 Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
* Fix translation of Qt::Key_MenuJoerg Bornemann2017-09-081-3/+2
| | | | | | | | | | | VK_MENU is the virtual key code for the Alt key, but Qt::Key_Menu is the context menu key which maps to VK_APPS. Now the menu key can be used to invoke the context menu on web pages. Task-number: QTBUG-58306 Change-Id: I8674ab84848b5c8732e4d0cf189909191b85d562 Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
* Update ChromiumAllan Sandfeld Jensen2017-09-081-0/+0
| | | | | | | | | | | | | | | | | | | Pulls in relevant security fixes upto Chome 61.0.3163.79 Changes: 609295469702 FIXUP: Support GN on MIPS64 hosts 0c3fee8fd9ae FIXUP: Optionally unbundle re2 10d8b35c35d1 [Backport] Fix for CVE-2017-5112 838d4d79ff42 [Backport] Fix for CVE-2017-5114 72c99b3ca20a [Backport] Fix for CVE-2017-5117 5d375e38c58d [Backport] Fix for CVE-2017-5118 bc703b5d9f97 [Backport] avformat/oggparsecelt: Do not re-allocate os->private 89de564d176a [Backport] FrameHostMsg_OpenURL_Params.resource_request_body needs to be validated. 5ebd47322d60 [Backport] Remove insecure code paths in portable NTLM. Change-Id: I8d8c93aab7f41a485c95878ce7aecb5997bbeb1c Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>
* Also set MIPS/Arm flags for host-buildsAllan Sandfeld Jensen2017-09-081-2/+2
| | | | | | | | | QT_ARCH is the current architecture, and if the host is Arm or MIPS, we also need the flags there. Task-number: QTBUG-61846 Change-Id: I38f826e061eff900f6e27f4de0fc913323cf5e3e Reviewed-by: Joerg Bornemann <joerg.bornemann@qt.io>
* Compile with Gestures disabledAlan Alpert2017-09-055-0/+16
| | | | | | Change-Id: Ibad2b8ebb90e79ff8337d994b2234eed5e230daa Reviewed-by: Romain Pokrzywka <romain.pokrzywka@gmail.com> Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
* Give up earlier on MIPS64 and don't tell users it is supportedAllan Sandfeld Jensen2017-09-051-2/+3
| | | | | | | | | Chromium doesn't currently build on MIPS64, so we shouldn't tell people it might work. Task-number: QTBUG-62655 Change-Id: I56e798cae6914cc8087f1a6a51f07383e81f86c1 Reviewed-by: Joerg Bornemann <joerg.bornemann@qt.io>
* Add detection for system re2Allan Sandfeld Jensen2017-09-036-0/+53
| | | | | | Change-Id: Ifa305045f3594f06b0ee106cd43f9d35853f8958 Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io> Reviewed-by: Michal Klocek <michal.klocek@qt.io>
* Add change file for Qt 5.6.3Antti Kokko2017-08-311-0/+73
| | | | | | | | Imported and expanded from 5.6 branch Task-number: QTBUG-62705 Change-Id: I89d060d18fec20eeb255625b8c78520163aeb83d Reviewed-by: Leena Miettinen <riitta-leena.miettinen@qt.io>
* Remove proprietary codec summary from configure.prfAllan Sandfeld Jensen2017-08-301-5/+0
| | | | | | | We already list this in summary of configure.json Change-Id: I03e5b5aa779541fd1ac367a1066b5c1846979cc1 Reviewed-by: Michal Klocek <michal.klocek@qt.io>
* Fix multilib builds with different archs of toolchain and systemAllan Sandfeld Jensen2017-08-291-1/+5
| | | | | | | | | Set host_cpu to ensure GN gets on the right path matching the host of the toolchain we give it in host_toolchain. Task-number: QTBUG-62673 Change-Id: I99d6dfdbe4cee30bc240049b656d1ec73becce8a Reviewed-by: Joerg Bornemann <joerg.bornemann@qt.io>
* [macOS] Warn about sending simulated touch events not working on macOSAlexandru Croitor2017-08-291-1/+11
| | | | | | | | | | Chromium itself does not really support processing touch events on macOS, but rather uses native gestures sent by the OS. Warn the user in case they send simulated QTouchEvents. Task-number: QTBUG-62130 Change-Id: If47f25bc06f3d6f99ba70164a585182354ed9b5a Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
* Close popup windows when their parents are destroyedAlexandru Croitor2017-08-291-0/+7
| | | | | | | | | | | | | | | | | | | | | Previously when a popup window was shown, and the user issued a command to close the only active main window (via a shortcut for example) with a subsequent call to deleteLater(), the main window would be closed and deleted but the popup would only be hidden, which led to the application loop to still be running and not quitting, even though there would be no visible window left. The closing of a popup is usually done in the QWidget destructor when the popup is still visible, but because we unset the parent right before the parent is destroyed (which sets visibility to false), the popup would not be closed, but only hidden. Thus this change makes sure to explicitly close the popup when its parent is destroyed. Task-number: QTBUG-62311 Change-Id: Ia0bbf327929af55aac19767971ab0acde5715e21 Reviewed-by: Viktor Engelmann <viktor.engelmann@qt.io>
* Update ChromiumAllan Sandfeld Jensen2017-08-291-0/+0
| | | | | | | | | Changes: dd11b14b60 Optionally unbundle re2 5caa35af6b Support GN on MIPS64 hosts Change-Id: I745f399477b182fa2216b879cac3d356ba0e69fd Reviewed-by: Joerg Bornemann <joerg.bornemann@qt.io>
* Fix upside down rendering of render-passes in software modeAllan Sandfeld Jensen2017-08-281-0/+1
| | | | | | | | | The software backend version of QSGLayer defaults to not mirroring vertically, where the OpenGL does, and we rely on that. Task-number: QTBUG-62112 Change-Id: Id5368728fd7046d2e4dc35bd4b2b61f2db35dac6 Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>
* Handle --explicitly-allowed-portsAllan Sandfeld Jensen2017-08-281-0/+6
| | | | | | | | | Chromium handles the flag for the render process, but with multi-process we need to enable it for the browser process as well. Task-number: QTBUG-62808 Change-Id: I1111dd7a2fd58876978ec5299bfb7abea8cb8487 Reviewed-by: Michal Klocek <michal.klocek@qt.io>
* Fix the detection of python2.exeHannah von Reth2017-08-211-2/+2
| | | | | | Change-Id: I6a8be77d1acfea34252a3b5c5a17e1792787a32b Reviewed-by: Florian Bruhin <qt-project.org@the-compiler.org> Reviewed-by: Joerg Bornemann <joerg.bornemann@qt.io>
* Add configure help file for the available optionsAndy Shaw2017-08-211-0/+13
| | | | | Change-Id: I5940db737f2c7b4c3cf831c72346cfeb2944bde8 Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
* Handle content::DropData::file_contentsJoerg Bornemann2017-08-183-1/+39
| | | | | | | | | | | | | | | | | | | | | | | | DropData::file_contents and DropData::file_description_filename are filled by Chromium if the user drags an image from a web page. Write the file's content into a file with the suggested file name in a temporary directory, and set the drop action to "move". This enables users to drag images from the browser to the desktop or a file browser. The file is moved by the client to the target location. The temporary directory is removed when the page is closed. Note that Chrome doesn't use this temporary directory trick, but employs techniques like XDS [1] on Linux to transfer the data via the native clipboard/DnD MIME object. Unfortunately QDrag doesn't support this. Support could be added, but I consider this solution as good enough. [1] https://www.freedesktop.org/wiki/Specifications/XDS/ Task-number: QTBUG-60790 Change-Id: I44f2b3170a124e861ed4131c421903d895b70715 Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>
* Update documentation on how to enable the proprietary codecsAndy Shaw2017-08-181-2/+2
| | | | | | | Change-Id: I8f8f1baff3824cb07057375a72b5ae6f0e09b5a7 Reviewed-by: Florian Bruhin <qt-project.org@the-compiler.org> Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io> Reviewed-by: Leena Miettinen <riitta-leena.miettinen@qt.io>
* Load libEGL and libGLES2 symbols implicitlyViktor Engelmann2017-08-141-32/+8
| | | | | | | | | | | | | | Instead of explicitly loading libraries from hard-coded locations, we now just call dlopen(NULL, RTLD_LAZY). This returns a handle to the host process'es context, which already contains the symbols of both these libraries, because we link against them. It was necessary to bypass LoadLibrary, because that expects a non-NULL file path, so we couldn't pass NULL through that interface. Task-number: QTBUG-57761 Change-Id: I29f037dfe542222b5188a33c7727c81a464a87bb Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io> Reviewed-by: Michal Klocek <michal.klocek@qt.io>
* Stop forwarding HoverEnter and HoverLeave QEventsJüri Valdmann2017-08-112-2/+3
| | | | | | | | | | | | | | | | | With QtWidgets the QHoverEvent handling is slightly incorrect (HoverEnter and HoverLeave triggering Q_ASSERT), quite unnecessary (Chromium works fine with just MouseMove events when mouse tracking is enabled), and mostly unused (QHoverEvents are only delivered if the WA_Hover widget attribute is set, which it usually is not). QtQuick however does not have the equivalent of QtWidgets mouse tracking, so to get mouse movement information into Chromium we have to use HoverMove QEvents. But the HoverEnter and HoverLeave QEvents are not used or useful for QtQuick either. Task-number: QTBUG-62200 Change-Id: I333de2b6adcc24544935d36645036aedb07e51ac Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>
* Remove dead code for detecting system SRTPAllan Sandfeld Jensen2017-08-115-45/+0
| | | | | | | | | We currently don't support unbundling SRTP because Chromium uses a too new unreleased version, but we were still testing for it and claiming to use the system one if found. Change-Id: I250f0d7fc1e09398b3196895bdd529d366cd0a86 Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>
* Update ChromiumAllan Sandfeld Jensen2017-08-111-0/+0
| | | | | | | | | | | | | | | | | Changes: 38528170ed Remove third_party/afl e155b257b2 Enable minimal optimizations when debug-symbols are disabled bcc2005d27 [Windows] Disable warning about mf.dll not being found on Windows e8b33d7a5f [Backport] Fix for CVE-2017-5093 e284f716a4 [Backport] Fix for CVE-2017-5095 176a2fd0d1 [Backport] Fix for CVE-2017-5097 584afa4c02 [Backport] Fix for CVE-2017-5102 f0e009af02 [Backport] Fix for CVE-2017-5103 f3a498db5d [Backport] Fix for CVE-2017-5092 and CVE-2017-5099 1ef056b863 [Backport] Fix for CVE-2017-5107 Change-Id: I16d6721a5ac97aae4d22ea3244c897b67f2296ce Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>
* Set web contents font setting to defaultAllan Sandfeld Jensen2017-08-031-0/+10
| | | | | | | | | | Chromium has since version 50 overridden the global font settings with the settings of every web contents created, so we need to first set the global settings in the web contents, to still follow system defaults. Task-number: QTBUG-62146 Change-Id: If10847c81beda08ecb7bfdf7556e39b1d2989754 Reviewed-by: Joerg Bornemann <joerg.bornemann@qt.io>
* Doc: List some command-line arguments that are useful during debuggingLeena Miettinen2017-08-031-1/+32
| | | | | | Task-number: QTBUG-61796 Change-Id: I76d3fec780796dd0f300c54a1bccecc50f7270e0 Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
* Fix signal name in simplebrowser example documentationJüri Valdmann2017-08-031-1/+1
| | | | | Change-Id: Id3bf1218e43609cdb471e087e2077d4c0c0e5153 Reviewed-by: Leena Miettinen <riitta-leena.miettinen@qt.io>
* Fix simplebrowser crash on exit while downloadingMichal Klocek2017-08-022-7/+5
| | | | | | | | | | | | | On webengine profile destruction all download items in progress are canceled. This triggered stateChanged of QWebEngineDownloadItem which called lambda function on already deleted object. Do not use lambda functions in this case. Change-Id: Ia1d359fe47204baa51f1380d1c3547c28550bc28 Reviewed-by: Joerg Bornemann <joerg.bornemann@qt.io> Reviewed-by: Viktor Engelmann <viktor.engelmann@qt.io>
* Fix reorder warning in proxy_config_service_qt.cppPeter Varga2017-07-311-2/+2
| | | | | | Task-number: QTBUG-61910 Change-Id: I894d1f180ba9952213b6f67a2445aa927dfd7e9b Reviewed-by: Kai Koehne <kai.koehne@qt.io>
* Fix demobrowser to not crash when switching to private browsing modePeter Varga2017-07-311-2/+0
| | | | | | | | | | Old QWebEnginePage is destructed by the QWebEngineView::setPage() call. No need to destruct it explicitly. Task-number: QTBUG-62147 Change-Id: I8ec33d5df618f69e4acf1667490df4a67dad9a16 Reviewed-by: Jüri Valdmann <juri.valdmann@qt.io> Reviewed-by: Kai Koehne <kai.koehne@qt.io>
* Fix typo in dictionary pathFlorian Bruhin2017-07-311-1/+1
| | | | | Change-Id: I398f88943e6f59781ad9227e2888cb25079b638c Reviewed-by: Kai Koehne <kai.koehne@qt.io>
* Doc: Add example code for using Greasemonkey attributes in scriptsLeena Miettinen2017-07-282-2/+33
| | | | | | Task-number: QTBUG-61788 Change-Id: Ie6c29f3999ea795a37ea444f56e40ddc70ca1c03 Reviewed-by: Kai Koehne <kai.koehne@qt.io>
* Avoid default handler in switchKai Koehne2017-07-271-1/+1
| | | | | Change-Id: I4533e28a2c1a338abdb1d373a0a3bfe598a5edce Reviewed-by: Peter Varga <pvarga@inf.u-szeged.hu>
* Fix logic to check for proxy settingsKai Koehne2017-07-252-35/+63
| | | | | | | | | | | | | | | | | | | The previous code tried to find out whether a user has set an application proxy by checking the type of the applicationProxy. This is wrong, because a system proxy will actually also change the applicationProxy type. Instead, we now rely on QNetworkProxyFactory::usesSystemConfiguration to decide whether to use QtNetwork's application proxy, or Chromium's logic for the system proxy. We also save the state of QNetworkProxy::useSystemConfiguration to be able to track changes. [ChangeLog][Networking] Fixed an issue where system proxy settings were not picked up correctly. Task-number: QTBUG-61910 Change-Id: I1d9af3f6006ba187266fe50c645f425a46632e41 Reviewed-by: Peter Varga <pvarga@inf.u-szeged.hu>
* Speculative stabilization of imeCompositionQueryEvent widget auto testPeter Varga2017-07-191-5/+7
| | | | | | | | Wait for receiver object to be set after show. Task-number: QTBUG-61816 Change-Id: I2eb62775d30b0f8f9ec3e76d60a924b56c811865 Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
* Doc: Align QtWebEngineWidgets overview with the one for the QtWebEngine moduleKai Koehne2017-07-191-2/+1
| | | | | Change-Id: If4db465b9764be80df7fe953be63fc1a40b60d75 Reviewed-by: Leena Miettinen <riitta-leena.miettinen@qt.io>
* Update Simple Browser exampleJüri Valdmann2017-07-1935-354/+750
| | | | | | | | | | | | | | | | | | | | | | | - Accept downloads and add a downloads list. - Fix toolbar icons being pixelated on hidpi screens by - enabling attribute AA_UseHighDpiPixmaps, and - replacing the 22x22 icons with 32x32 versions. - Move favicon selection to WebView to reduce duplication. - Replace UrlLineEdit with a standard QLineEdit using a QAction for the favicon and setClearButtonEnabled(true) for the clear button. - Fix bug where the "File -> New Tab" action would create background tabs because the QAction::triggered(bool) signal was connected to the TabWidget::createTab(bool) slot with the bool argument having a completely different meaning between the two. - Make the toolbar unmovable. Nobody wants to move the toolbar. - Add tooltips to toolbar buttons. - Add tooltips to the tab bar (page titles). - Stop adding icons to menu items only to disable them right after. Task-number: QTBUG-60655 Change-Id: I10cc0fa82dbf39281bbdbbf9ef901e1b26402f80 Reviewed-by: Leena Miettinen <riitta-leena.miettinen@qt.io> Reviewed-by: Michal Klocek <michal.klocek@qt.io>
* Remove third_party/afl from Chromium snapshotKai Koehne2017-07-191-0/+1
| | | | | | Task-number: QTBUG-61954 Change-Id: I681f7adaab1e0ef1ec162fa98c4a70569e8c3948 Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
* Fix C-ABI breakageMichal Klocek2017-07-192-1/+124
| | | | | | | | Re-export missing C memory handling functions. Task-number: QTBUG-61521 Change-Id: I8f94d93a70c81117735a9610e391a1e31c54f15a Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
* Support command-line argument --force-webrtc-ip-handling-policyAllan Sandfeld Jensen2017-07-181-0/+6
| | | | | | | | | | This command-line argument makes it possibly to block exposure of internal IP addresses when WebRTC access hasn't been granted, using --force-webrtc-ip-handling-policy=default_public_interface_only Task-number: QTBUG-57505 Change-Id: I0cddd1b20e0814811894204cb31e0c463a75f7be Reviewed-by: Kai Koehne <kai.koehne@qt.io>
* Yield error if the build directory contains spacesJoerg Bornemann2017-07-171-4/+7
| | | | | | Task-number: QTBUG-61275 Change-Id: I7e741ffaaa4044b3b61b6df06ea3eab181db9c97 Reviewed-by: Michal Klocek <michal.klocek@qt.io>
* Fix propagation of unhandled key press eventsJoerg Bornemann2017-07-142-3/+13
| | | | | | | | | | | | | | | Unhandled key presses for printable keys were not received by the parent widget anymore. This was a regression from 5.8.0. The propagation is suppressed if NativeWebKeyboardEvent::skip_in_browser is true. Commit 4501b9d8 accidentally removed the wrong skip_in_browser assignment. Task-number: QTBUG-61621 Change-Id: I7eafa1fac5fb9a7edc4af2bc1aac21c106264713 Reviewed-by: Peter Varga <pvarga@inf.u-szeged.hu>
* Properly document third party code in examplesKai Koehne2017-07-1317-29/+140
| | | | | | | | | | | Move files from marked, markdown.css to a 3rdparty directory, and properly document them with a qt_attribution.json file. Finally, reference the (automatically generated) documentation in the respective examples documentation. Task-number: QTBUG-61706 Change-Id: I8fd3f894e6e81647bc4804df784b1e00b83d12d6 Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>
* Examples: Add recipebrowser to top-level .pro fileKai Koehne2017-07-131-1/+2
| | | | | Change-Id: I7d22a9c2a4f4aed1f364e672985da357158467e7 Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>
* Update ChromiumMichal Klocek2017-07-131-0/+0
| | | | | | | | | | | | | | Pulls following changes: 1a14be1 Enable using gnu thin archives on Linux 296b240 Silence gcc -Waddress warnings in logging.h fabd7e0 Fix building without git installed 1173dda Do not export c memory handling functions 25ceaa6 Do not launch zygote processes in single-process mode 721a4d1 Carry over user-agent override when opening new windows Change-Id: If48223d76fbb35f1847e416a7f244e4b6ed85f33 Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>
* Document about popups not appearing on Windows when in fullscreen modeAlexandru Croitor2017-07-132-0/+7
| | | | | | | | | | | | | | On Windows there is an issue that an OpenGL-backed fullscreen window will prevent other top-level windows from appearing on top of it (for example a select / combo box popup). This appears to be a limitation of the Windows platform compositor (DWM). The workaround is to call QWindowsWindowFunctions::setHasBorderInFullScreen on the QWindow which will show the fullscreen WebEngine view. Task-number: QTBUG-61563 Change-Id: I5e0f08ef49de6119ef7910cec2b32ea267301c18 Reviewed-by: Leena Miettinen <riitta-leena.miettinen@qt.io>
* Take into account the value of the --touch-events Chromium switchAlexandru Croitor2017-07-112-1/+43
| | | | | | | | | | | | | | | | | | | | | | | | | | | In Chromium 56 the --touch-events switch controls both the availability of the Touch Events API in JavaScript (presence of 'ontouchstart' in 'window' object), and whether touch events are dispatched at all. In Chromium 57, the switch controls only the Touch Events API availability, and touch events are always dispatched. In Qt 5.9.0 which is based on Chromium 56, we always dispatched touch events, ignored the value of --touch-events, and determined the availability of the Touch Events API by checking if QTouchDevice lists any touch screen devices (essentially Chromium's --touch-events=auto option). This commit changes the behavior of WebEngine to match that of Chromium 57, so that users can choose to enable or disable the Touch Events API via the --touch-events switch, whereas the default will be 'auto' mode. Touch events will always be dispatched as usual. Users that wish to stop dispatching touch events can install an event filter on WebEngine's view focus proxy. Task-number: QTBUG-61045 Change-Id: I07404af3336619869aa87a90a1b426036548dd55 Reviewed-by: Leena Miettinen <riitta-leena.miettinen@qt.io> Reviewed-by: Kai Koehne <kai.koehne@qt.io>
* Fix "Could not share GL contexts" warnings on WindowsAlexandru Croitor2017-07-111-0/+11
| | | | | | | | | | | Make sure that a non-Core Profile OpenGL Context is created on the Chromium side, so that sharing between the Qt global context and the Chromium ones works. Change-Id: Ifc5f39268395615fe50c8aa9467f833c0de233a8 Reviewed-by: Joerg Bornemann <joerg.bornemann@qt.io> Reviewed-by: Kai Koehne <kai.koehne@qt.io> Reviewed-by: Viktor Engelmann <viktor.engelmann@qt.io>
* [macOS] Use the OpenGL CoreProfile when the global shared context doesAlexandru Croitor2017-07-113-3/+20
| | | | | | | | | | | | | | | | | | | | Previously when a default QSurfaceFormat was set with an OpenGL Core profile, all the contexts created on the Qt side would obey the profile, but Chromium would still use the Compatibility profile for its contexts leading to warnings when trying to create shared contexts. The fix is to check which OpenGL profile is used in the Qt global shared context, and pass that information along to Chromium. Note that this works only on macOS for now, and the default non-Core profile is used on other platforms, even though Core was requested. Passing CoreProfile to Chromium on Windows and Linux currently leads to crashes. Task-number: QTBUG-60605 Change-Id: I27a77091923624d19ccc2019953a5b07f9282916 Reviewed-by: Peter Varga <pvarga@inf.u-szeged.hu> Reviewed-by: Kai Koehne <kai.koehne@qt.io>
* Call stopFinding, when navigating awayViktor Engelmann2017-07-063-3/+7
| | | | | | | | | | | When one searches for text on one page and then navigates away, results for the search-term are also highlighted on the new page. To stop this from happening, we now call adapter->stopFinding() when we navigate away from a page. Task-number: QTBUG-61506 Change-Id: I09e064d7788b12eae0a67c01e4f5872d94924617 Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
* Increase debug symbol level on Windows to generate all Chromium symbolsAlexandru Croitor2017-07-041-2/+7
| | | | | | | | | | | Debug symbol level 1 is not enough to generate all debug symbols on Windows. The symbols for the files found in src/core are generated with symbol_level=1, but no symbols are generated for the files in src/3rdparty. Change-Id: I30729981d5956c1c6a8040008bc00af1f19c15d2 Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org> Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
generated by cgit v1.2.3 (git 2.25.1) at 2024-05-13 12:44:36 +0000