1. 06 Aug, 2020 2 commits
  2. 05 Aug, 2020 1 commit
  3. 03 Aug, 2020 1 commit
  4. 01 Aug, 2020 1 commit
  5. 31 Jul, 2020 1 commit
  6. 28 Jul, 2020 1 commit
  7. 23 Jul, 2020 2 commits
  8. 14 Jul, 2020 1 commit
  9. 13 Jul, 2020 1 commit
  10. 11 Jul, 2020 1 commit
  11. 10 Jul, 2020 1 commit
    • Jonathan Marten's avatar
      Fix proxy configuration where WebEngine is not the default · efb58d59
      Jonathan Marten authored
      Commit 2b45b2af introduced checking and synchronisation of the KIO proxy
      configuration with WebEngine (which can only use a limited set of the
      available options).  However, if WebEngine is not the default part
      (webengineIsDefault in KonqMainWindow::updateProxyForWebEngine()), the
      Qt application proxy is unconditionally set to NoProxy.  This may not be
      correct if the user has set proxy environment variables suitable for
      WebEngine but it is not the default.
      
      In order to cover the case where WebEngine is not the default but the user
      may wish to switch to it later, if it is not the default then assume that
      the existing proxy settings are as intended and do not change them.
      efb58d59
  12. 28 Jun, 2020 1 commit
  13. 24 Jun, 2020 1 commit
  14. 18 Jun, 2020 2 commits
  15. 17 Jun, 2020 2 commits
  16. 14 Jun, 2020 1 commit
    • Stefano Crocco's avatar
      Ensure that WebEnginePart uses proxy settings from KCM · 2b45b2af
      Stefano Crocco authored
      Summary:
      Force WebEnginePart to follow the global KDE proxy settings.
      
      QtWebEngine uses the proxy set with QNetworkProxy::setApplicationProxy, which
      means that it ignores the KDE proxy settings chosen by the user.
      
      To force QtWebEngine to respect the user's preferences, read the proxy settings
      using KProtocolManager and call QNetworkProxy::setApplicationProxy
      appropriately.
      
      QtWebEngine only supports a small subset of the options provided by the
      proxy KCM: if the current configuration isn't supported, the user is
      warned and asked how to proceed.
      
      If the default HTML engine is not QtWebEngine,
      QNetworkProxy::setApplicationProxy is still called in case of a
      supported configuration, but nothing is done in case of an unsupported
      configuration.
      
      Reviewers: dfaure
      
      Differential Revision: https://phabricator.kde.org/D29066
      2b45b2af
  17. 13 Jun, 2020 1 commit
  18. 07 Jun, 2020 1 commit
  19. 02 Jun, 2020 4 commits
  20. 31 May, 2020 1 commit
  21. 23 May, 2020 5 commits
  22. 21 May, 2020 1 commit
  23. 19 May, 2020 1 commit
  24. 17 May, 2020 1 commit
  25. 10 May, 2020 3 commits
  26. 09 May, 2020 1 commit
  27. 05 May, 2020 1 commit