ubuntu-webapps-bugs team mailing list archive

[Chris Coulson <chrisccoulson@xxxxxxxxxx>]

Public bug reported:

Currently OxideQQuickWebView proxies a bunch of calls through to
qquick::ContentsView. I've been thinking about devtools recently, and I
want to make the webview inspectable (ie, make it support displaying
Chromium's docked devtools UI and have it be invokable from the context
menu). To make the devtools panel undockable, there will be a new client
of qquick::ContentsView which will essentially be a window with a
WebContents embedder in it. It would be nice to not have to duplicate a
bunch of code to just proxy calls through to ContentsView.

** Affects: oxide
     Importance: Medium
         Status: Triaged

** Changed in: oxide
   Importance: Undecided => Medium

** Changed in: oxide
       Status: New => Triaged

-- 
You received this bug notification because you are a member of Ubuntu
WebApps bug tracking, which is subscribed to Oxide.
https://bugs.launchpad.net/bugs/1667822

Title:
  Investigate making qquick::ContentsView a QQuickItem

Status in Oxide:
  Triaged

Bug description:
  Currently OxideQQuickWebView proxies a bunch of calls through to
  qquick::ContentsView. I've been thinking about devtools recently, and
  I want to make the webview inspectable (ie, make it support displaying
  Chromium's docked devtools UI and have it be invokable from the
  context menu). To make the devtools panel undockable, there will be a
  new client of qquick::ContentsView which will essentially be a window
  with a WebContents embedder in it. It would be nice to not have to
  duplicate a bunch of code to just proxy calls through to ContentsView.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1667822/+subscriptions