1. Oct 07, 2014
  2. Oct 03, 2014
  3. Sep 29, 2014
  4. Sep 12, 2014
  5. Sep 11, 2014
    • Jocelyn Turcotte's avatar
      Use the same version scheme as other Qt modules · 88d5cb11
      Jocelyn Turcotte authored
      
      After trying to get rid of all private header includes, the last
      standing one is qplatformnativeinterface.h even though its name
      previously suggested that it isn't private.
      
      This would be a complicated piece to expose publically in a way both
      flexible and binary compatible, and is a task heavy enough to
      justify committing to follow Qt's release cycle.
      
      The QML import version remains to 1.0 and will be incremented the
      same manner as QtQuick itself does.
      
      Change-Id: I6fab5f229d9f79dbc7a3e82d65ad324020929863
      Reviewed-by: default avatarMichael Bruning <michael.bruning@digia.com>
      88d5cb11
    • Jocelyn Turcotte's avatar
      Remove unnecessary private header includes · 50f79d4b
      Jocelyn Turcotte authored
      
      Most importantly, get rid of QOpenGLContextPrivate::globalShareContext
      which will be removed before the final.
      
      Change-Id: I5796fa822d2962c21fd8b6d8d3c196686d536e3d
      Reviewed-by: default avatarAndras Becsi <andras.becsi@digia.com>
      50f79d4b
  6. Sep 10, 2014
  7. Sep 05, 2014
    • Peter Varga's avatar
      Fix url stored in LoadRequest · daf3a688
      Peter Varga authored
      
      The test_urlProperty() qml test has failed because the active url was
      stored in LoadRequest in case of LoadFailedStatus.
      With this fix the loadRequest stores the url of that page which implies
      the request.
      
      Change-Id: I6aab814a4a7d3b47043b03fccde3d9995b40d8fa
      Reviewed-by: default avatarPierre Rossi <pierre.rossi@gmail.com>
      daf3a688
  8. Sep 02, 2014
    • Pierre Rossi's avatar
      Don't forward loading of error pages to the API layer · ede95c2a
      Pierre Rossi authored
      
      The fact that the error pages are HTML and get loaded through the
      same mechanism should be kept an implementation detail and not be
      considered as a new load in the API sense.
      Also implement HasErrorPage for good measure and remove an anoying
      warning from the demo browser.
      
      The issue of the url not being changed remains in the QML test (but
      it doesn't affect a typical browser-like UI since the user input is
      still there untouched in the address bar), just make sure that failure
      does not affect the later checks. It also seems like we have a focus
      problem somehow, but the test should probably use a click for that
      matter.
      
      Change-Id: Ib5e363981a11287fdf4bfe84b93c999d96ed8087
      Reviewed-by: default avatarJocelyn Turcotte <jocelyn.turcotte@digia.com>
      ede95c2a
    • Pierre Rossi's avatar
      Settings for Qt quick · 33a0ed37
      Pierre Rossi authored
      
      Expose settings in experimental for now.
      Simply use the global/per-view mechanism as a group level
      in between seems like overkill.
      
      Change-Id: I7610e9c7765ccb41674702acdd24a52b87716da8
      Reviewed-by: default avatarJocelyn Turcotte <jocelyn.turcotte@digia.com>
      33a0ed37
  9. Aug 29, 2014
  10. Aug 28, 2014
  11. Aug 26, 2014
  12. Aug 21, 2014
  13. Aug 20, 2014
    • Jocelyn Turcotte's avatar
      Propagate the page's screen coordinates when the top-level window moved · 7717f941
      Jocelyn Turcotte authored
      
      This fixes a regression after the 37 upgrade where the select popups
      would have the wrong position. Adjust to the new behavior and also
      avoid doing a mapToGlobal of the position received in InitAsPopup.
      
      RWHV::SetBounds has been giving us screen coordinates since the
      Chromium 33 update, but popup locations somehow managed to work
      properly through some side-effect sorcery.
      
      This also fixes the value of window.screen[XY] in JavaScript which
      wasn't updated when the window was moved.
      
      Change-Id: I544499bafedccfb7d389b4abc48f1386c398473f
      Reviewed-by: default avatarPierre Rossi <pierre.rossi@gmail.com>
      7717f941
  14. Aug 19, 2014
    • Michael Brüning's avatar
      Tell ANGLE to enable multithread protection. · 33b4d6f1
      Michael Brüning authored
      
      This is done on initialization of the Web Engine as this should
      happen before any contexts and Direct 3D devices are created.
      
      It makes D3D9 create a device with the D3DCREATE_MULTITHREADED
      flag and makes D3D11 enable multithread protection using the
      ID3D10Multithread interface.
      
      Depends on the appropriate counterpart in QtANGLE.
      
      Change-Id: I8204de2f8ebe993273ff9f11af55caacb1290e4e
      Reviewed-by: default avatarAllan Sandfeld Jensen <allan.jensen@digia.com>
      33b4d6f1
  15. Aug 12, 2014
  16. Aug 09, 2014
    • Pierre Rossi's avatar
      Ground work for Settings/Preferences · 37fcb151
      Pierre Rossi authored
      
      Core interface to expose toggling some of the WebPreferences
      for now and most probably some of the WebRuntimeFeatures soon.
      
      The whole dummy settings business is meant to keep things
      from breaking too much when bisecting, because it is assumed
      that there are always valid settings for a given adapterClient.
      
      Change-Id: Ic0a62bcb5af8c0254436dc770b43cde5016c3bbd
      Reviewed-by: default avatarAllan Sandfeld Jensen <allan.jensen@digia.com>
      37fcb151
  17. Aug 07, 2014
  18. Aug 06, 2014
  19. Aug 04, 2014
    • Pierre Rossi's avatar
      Expose better error information in loadRequest. · 7d90b441
      Pierre Rossi authored
      
      Use the chromium localized error strings for that purpose, otherwise the
      error description is always empty.
      
      While we're at it, let's tap into the chromium error pages, which should
      hopefully make sense for most errors, and add some static asserts to
      check that the qt quick enum and the core one are in sync.
      
      Change-Id: Icf8fa7c3bf4a674c60a10950422135fb6930447a
      Reviewed-by: default avatarAndras Becsi <andras.becsi@digia.com>
      7d90b441
    • Pierre Rossi's avatar
      s/QWebEngine/QtWebEngine/g · 35d66ce4
      Pierre Rossi authored
      
      and make it a namespace
      
      Change-Id: I15c1af8c7d0d8ab213cdf7945109263fe461d2ac
      Reviewed-by: default avatarAndras Becsi <andras.becsi@digia.com>
      35d66ce4
    • Jocelyn Turcotte's avatar
      Don't inherit from Qt private types · 1c2a4da1
      Jocelyn Turcotte authored
      
      Do the d_ptr magic ourselves to avoid having to include private
      headers from qtcore, qtgui and qtdeclarative.
      
      It is hackish to hide QObject's d_ptr member to have the macros
      working in a public class, but if anything goes wrong we just
      need to replace the private macro convenience while maintaining
      the binary compatibility of the stored extra opaque pointer.
      
      Change-Id: Idb92f4f902826bef9068a5c2ef6ea31fc3fa15b2
      Reviewed-by: default avatarAndras Becsi <andras.becsi@digia.com>
      1c2a4da1
  20. Aug 01, 2014
  21. Jul 26, 2014
  22. Jul 24, 2014
  23. Jul 21, 2014