1. Mar 24, 2015
  2. Mar 20, 2015
    • Pierre Rossi's avatar
      Introduce mock UIDelegates for testing. · a2f1431e
      Pierre Rossi authored
      
      Switch JS dialogs test to using this over the testsupport
      plugin.
      
      This is a less intrusive approach that lives as self contained qml
      modules within the test infrastructure. As an added benefit, it
      covers the UI delegation logic from end to end, including what
      happens in ui_delegates_manager.cpp.
      
      Change-Id: I1cc0afaf5514d53e1f3b4b0682379dd2d8d8a913
      Reviewed-by: default avatarAndras Becsi <andras.becsi@theqtcompany.com>
      a2f1431e
  3. Mar 18, 2015
    • Robin Burchell's avatar
      QQuickWebEngineScript: Add a sourceUrl property to complement sourceCode. · e9c82ddc
      Robin Burchell authored
      
      QtQuick doesn't have a convenient interface to interact with files, and even if
      that were the case, it would either be more awkward (and with increased overhead
      -- the price of an extra QObject, property, signal, etc) just to fetch the
      contents.
      
      So, we provide a convenience to allow fetching a user script from a file.
      
      Setting the sourceCode directly will reset sourceUrl (if it is set), and setting
      sourceUrl will ultimately result in a sourceCode change signal, too.
      
      Change-Id: Iee5abc0d719e2aeeacf1265f695b5a7efee9e0e8
      Reviewed-by: default avatarAndras Becsi <andras.becsi@theqtcompany.com>
      e9c82ddc
  4. Mar 16, 2015
  5. Mar 13, 2015
    • Peter Varga's avatar
      Support HTML5 form validation feature · 60d8d3dc
      Peter Varga authored
      
      HTML5 provides built-in form validation that is supported by chromium.
      The form validation messages should be shown by the browser therefore
      new MessageBubble UI element has been added to Quick and Widget
      implementations.
      This patch implements chromium's form validation events and shows the
      messages in a MessageBubble.
      
      Change-Id: I0c8f4f102823117e2bfb16ff8a4c503635491939
      Reviewed-by: default avatarAndras Becsi <andras.becsi@theqtcompany.com>
      60d8d3dc
  6. Mar 12, 2015
  7. Mar 11, 2015
  8. Mar 09, 2015
  9. Mar 06, 2015
  10. Mar 04, 2015
  11. Mar 02, 2015
  12. Feb 22, 2015
  13. Feb 19, 2015
  14. Feb 18, 2015
    • Pierre Rossi's avatar
      Move navigationHistory out of experimental · 6717d581
      Pierre Rossi authored
      
      Add an offset role to the models.
      Implement goBackAndForward that uses this offset.
      
      Also add a complete model, items, that includes current
      navigation entry (at offset 0) to allow for the Firefox-style
      single menu, and add that one to the nano browser example.
      
      The models are now instantiated lazily as it's unlikely the
      three models will be used by the same app.
      
      Change-Id: Ib551738611497c7eb9c501f045cda315968a2ada
      Reviewed-by: default avatarAndras Becsi <andras.becsi@theqtcompany.com>
      6717d581
  15. Feb 16, 2015
  16. Feb 13, 2015
  17. Feb 12, 2015
  18. Feb 06, 2015
  19. Feb 05, 2015
    • Allan Sandfeld Jensen's avatar
      Add settings to WebEngineProfiles · 4ef5831a
      Allan Sandfeld Jensen authored
      
      This patch adds settings to profiles so common settings might be shared
      among all pages in a profile. The former global settings are now replaced
      by the settings of the default profile.
      
      Change-Id: I544420e07beeb52ef29b2360bc7929402650cd07
      Reviewed-by: default avatarAndras Becsi <andras.becsi@theqtcompany.com>
      4ef5831a
    • Jocelyn Turcotte's avatar
      Propagate unhandled key events to the QtWebEngine view's parent · faec509a
      Jocelyn Turcotte authored
      
      This allows applications to receive unhandled key events from the page
      by setting an event handler on the view's parent widget/item, like
      it was possible with QtWebKit.
      
      This is different in that events first have to asynchronously go
      through the QtWebEngineProcess. If the WebEngine view has the
      keyboard focus, the events will be consumed inconditionally by the
      RenderWidgetHostViewQtDelegates, and a copy will be resent to the
      view's parent if it wasn't consumed.
      
      This sends it to the parent instead of the QWebEngineView directly
      since those are only unhandled events, unlike with other widgets
      where you can first intercept events. It is done that way also in
      cases where the QWebEngineView would be be the focus widget directly
      in the future, instead of the RWHV.
      
      If applications want to intercept key events before they reach the
      page, they need to use an event filter on the QWebEngineView's
      children or globally on the application.
      
      Change-Id: I3b48f5212d3f238a1c0497cec1db6ae3badbad26
      Reviewed-by: default avatarAndras Becsi <andras.becsi@theqtcompany.com>
      faec509a
  20. Feb 02, 2015
  21. Jan 29, 2015
  22. Jan 28, 2015
  23. Jan 27, 2015
  24. Jan 23, 2015
  25. Jan 22, 2015
    • Jocelyn Turcotte's avatar
      Replace the inspectable property with an environment variable · 35630628
      Jocelyn Turcotte authored
      
      The current implementation would enable or disable the inspector
      globally when the inspectable property was set on a WebEngineView,
      overwriting the value previously set by other pages.
      
      Instead of havind default port for the debugging server and having
      to enable debugging on individual pages, use an environment variable,
      QTWEBENGINE_REMOTE_DEBUGGING, to enable the debugging server for the
      whole application at the same time as specifying the port. The format
      is the same as for QTWEBKIT_INSPECTOR_SERVER in QtWebKit.
      
      QTWEBENGINE_REMOTE_DEBUGGING is set by default in quicktestbrowser
      to ease development.
      
      This also keeps the input reading from the --remote-debugging-port
      command line switch for convenience, but its usage should be
      considered internal.
      
      This patch also take the opportunity to remove the unused
      DevToolsHttpHandlerDelegateQt::m_browserContext and to move the
      ownership from ContentBrowserClientQt to WebEngineContext since
      the list of inspectable pages isn't bound to the BrowserContext
      anyway.
      
      Change-Id: I772687f88f4feee0cc14dd182b0129cc0ea384dd
      Reviewed-by: default avatarPierre Rossi <pierre.rossi@theqtcompany.com>
      35630628
    • Adam Kallai's avatar
      Fix the tst_navigationHistory QML testcase · 9c852a04
      Adam Kallai authored
      
      When the ListView component is created from the QQuickWebEngineHistoryListModel model.
      It requires an adapter to get the currentNavigationEntryIndex and navigationEntryCount
      for the QQuickWebEngineHistoryListModel::rowCount.
      Add the default rowCount value while the adapter is not unavailable because of the lazy
      adapter initialization.
      
      Change-Id: Id80d6f56adfea613bdc2c13d9caa1a12f50fddca
      Reviewed-by: default avatarAllan Sandfeld Jensen <allan.jensen@theqtcompany.com>
      Reviewed-by: default avatarAndras Becsi <andras.becsi@theqtcompany.com>
      9c852a04
  26. Jan 20, 2015
  27. Jan 16, 2015
  28. Jan 12, 2015
    • Andras Becsi's avatar
      Add QML download API · e6a74159
      Andras Becsi authored
      
      This patch exposes downloadStarted and downloadFinished
      signals on the WebEngineProfile to notify about downloads.
      The WebEngineDownloadItem exposes a subset of Chromium's
      content::DownloadItem functionality.
      For now we expose minimal requirements to be able to control
      downloads in QML but this can be extended in the future.
      This patch also adds a DownloadView to quicktestbrowser
      to demonstrate the usage of the new API.
      
      [ChangeLog][QtWebEngineQML] Add QtQuick download API
      
      Change-Id: I8d8f0daf02c4e0151000427fc2a4b37d28b9db52
      Reviewed-by: default avatarJocelyn Turcotte <jocelyn.turcotte@digia.com>
      e6a74159