1. Apr 13, 2019
  2. Apr 05, 2019
  3. Apr 03, 2019
  4. Apr 01, 2019
  5. Mar 26, 2019
  6. Mar 21, 2019
  7. Mar 19, 2019
  8. Mar 07, 2019
  9. Mar 01, 2019
  10. Feb 27, 2019
  11. Feb 26, 2019
  12. Feb 22, 2019
  13. Feb 21, 2019
  14. Feb 19, 2019
  15. Feb 08, 2019
  16. Feb 06, 2019
    • Kirill Burtsev's avatar
      Web Notifications API · f4ca67aa
      Kirill Burtsev authored
      
      Implements API for end-user notifications.
      
      Co-authored by Allan Sandfeld Jensen
      
      [ChangeLog][Profile] Support for Web Notifications API
      for end-user notifications through QWebEngineNotification
      
      Task-number: QTBUG-50995
      Fixes: QTBUG-51191
      Change-Id: Icebaaa05275a713e801f1f8ecdaaec725fa264c8
      Reviewed-by: default avatarAllan Sandfeld Jensen <allan.jensen@qt.io>
      f4ca67aa
  17. Feb 04, 2019
    • Michal Klocek's avatar
      Move QWebEngineUrlRequestInterceptor::intercept to ui thread · 5e92adf5
      Michal Klocek authored
      
      Currently interceptor sufferers thread safety issues, when
      custom profiles are deleted, interceptor is set to be nullptr,
      however it can be still referenced in IO thread. Since
      profile was split to ui and io part, where io part can outlive
      the ui part, this can boost thread safety issues.
      Since QWebEngineUrlRequestInterceptor is living on ui thread
      simplify the logic move intercept call to ui thread.
      This fixes the issue of referencing interceptor in io thread.
      
      Add new method to install interceptor setUrlRequestInterceptor,
      and deprecate old one. Update interceptor install method name
      on page to match the profile one.
      
      Task-number: QTBUG-69844
      Change-Id: I5dd2b6b734fd91906cccc6c1408ffbe7b1b4250c
      Reviewed-by: default avatarAllan Sandfeld Jensen <allan.jensen@qt.io>
      5e92adf5
  18. Feb 01, 2019
  19. Jan 31, 2019
  20. Jan 30, 2019
  21. Jan 21, 2019
  22. Jan 08, 2019
  23. Jan 07, 2019
  24. Dec 12, 2018
  25. Dec 10, 2018
    • Szabolcs David's avatar
      Move printing operation to a new thread · 8124f0bc
      Szabolcs David authored
      
      Printing operations were blocking the UI thread, so applications
      were irresponsive when printing in large size or high resolution.
      Introduce a new worker for the painting logic and use shared pointers
      to carry the data around and avoid copying PDF data between threads.
      
      Task-number: QTBUG-68561
      Change-Id: I30633380b75acd14f1a1df87985c99540168a9f1
      Reviewed-by: default avatarMichael Brüning <michael.bruning@qt.io>
      8124f0bc
  26. Oct 31, 2018
  27. Oct 29, 2018
    • Peter Varga's avatar
      Keep visibility of WebContents when restoring history · 4ecd0d7b
      Peter Varga authored
      
      For restoring history a new WebContents is needed to be created.
      Make it visible if the old WebContents was.
      
      Task-number: QTBUG-71400
      Change-Id: Ica10545e11413eb4da553f4976f9bf0c20125846
      Reviewed-by: default avatarJüri Valdmann <juri.valdmann@qt.io>
      4ecd0d7b
    • Jüri Valdmann's avatar
      Stop showing speculative frames · 36d230c4
      Jüri Valdmann authored
      Chromium creates "speculative" frames (RenderFrameHost and company) for pending
      cross-process navigations (and maybe other navigations too). For example, a
      redirect from http://qt.io to https://qt.io
      
       will trigger this, as described in
      the bug report.
      
      These speculative frames are loading in the background and only shown once they
      are officially ready (as decided by the RenderFrameHostManager and signaled to
      WebContentsObserver::RenderViewHostChanged). At least, this is how it's supposed
      to work and how it works in Chrome. In WebEngine, however, we actually show
      these speculative frames as soon as they are created and before they are ready.
      This runs into the problem that the if the speculative frame is dropped (instead
      of committed), then Chromium will not ask us to re-show the old frame (since it
      hasn't actually asked to us to show the new frame, it naturally assumes we are
      still showing the old one).
      
      Fixes: QTBUG-68727
      Change-Id: I9d53035ce60e3a002d5412d4473d940a32644b5d
      Reviewed-by: default avatarAllan Sandfeld Jensen <allan.jensen@qt.io>
      36d230c4
  28. Oct 23, 2018
  29. Oct 17, 2018
    • Allan Sandfeld Jensen's avatar
      Add setRequestInterceptor to QWebEnginePage · 17bd9d9d
      Allan Sandfeld Jensen authored
      
      Makes it possible to make page specific intercepts, and is at the same
      time safer by running in the UI-thread.
      
      [ChangeLog][QtWebEngineWidgets][QWebEnginePage] Added
      setRequestInterceptor, similar to the same call on profile except
      it operates on a per-page basis and on the UI-thread.
      
      Change-Id: Id5a7173156c25d0f030f00b6ef314d283c7c8cdd
      Reviewed-by: default avatarJüri Valdmann <juri.valdmann@qt.io>
      17bd9d9d
    • Allan Sandfeld Jensen's avatar
      Make it possible to enable OCSP on Linux · 0b1025b8
      Allan Sandfeld Jensen authored
      
      The code follows Chromium and also set a CertNetFetcher on both Linux
      and macOS, but it appears to be currently unused.
      
      [ChangeLog][QWebEngineProfile] A profile can now be designated to
      download OCSP records and thus enable OCSP verification on Linux.
      
      Task-number: QTBUG-58059
      Task-number: QTBUG-71164
      Change-Id: I84fd34d4351cb7aa4417ce4058f97bad4b8d0cd4
      Reviewed-by: default avatarJüri Valdmann <juri.valdmann@qt.io>
      0b1025b8
  30. Oct 04, 2018
  31. Oct 01, 2018
  32. Sep 24, 2018