1. 22 Jun, 2022 1 commit
    • Kyle Kienapfel's avatar
      tweak API usage in qt_web_browser.cpp · 31c6ba7e
      Kyle Kienapfel authored
      In testing future versions of Qt I forgot to compile with `YUZU_USE_QT_WEB_ENGINE`, so with that flag enabled there are two issues that cropped up.
      
      1. yuzu currently uses setRequestInterceptor, added in Qt 5.6, deprecated in 5.13 with this explaination at https://doc.qt.io/qt-5/qwebengineprofile-obsolete.html
      Interceptors installed with this method will call QWebEngineUrlRequestInterceptor::interceptRequest on the I/O thread. Therefore the user has to provide thread-safe interaction with the other user classes. For a duration of this call ui thread is blocked. Use setUrlRequestInterceptor instead.
      
      2. QWebEngineSettings::globalSettings() pointer no longer exists in later versions of Qt
      
      From what I can tell, QtNXWebEngineView doesn't need to set these globally,
      when we make changes to settings(), QtWebEngineView::page() creates the page
      object if it doesn't exist yet. I don't see the page object being destroyed
      or otherwise replaced, except via destroying the QtNXWebEngineView object.
      
      The globalSettings() make sense if Pages or Views objects are being
      created outside of yuzu's control.
      
      To test this I've compared what BrowseNX and Odyssey's Action guide do in mainline 1049 and this PR.
      
      For now we're going to go up the chain to QWebEngineProfile::defaultProfile()->settings()
      31c6ba7e
  2. 11 Jun, 2022 12 commits
  3. 10 Jun, 2022 2 commits
  4. 08 Jun, 2022 1 commit
  5. 07 Jun, 2022 4 commits
  6. 06 Jun, 2022 2 commits
  7. 05 Jun, 2022 4 commits
  8. 04 Jun, 2022 3 commits
  9. 03 Jun, 2022 2 commits
  10. 02 Jun, 2022 7 commits
  11. 01 Jun, 2022 2 commits