ubuntu-webapps-bugs team mailing list archive

Thread
Date

[Bug 1494944] [NEW] oxide::WebFrame should own OxideQQuickWebFrame (not the other way around)

To: ubuntu-webapps-bugs@xxxxxxxxxxxxxxxxxxx
From: Chris Coulson <chris.coulson@xxxxxxxxxxxxx>
Date: Fri, 11 Sep 2015 21:25:30 -0000
Reply-to: Bug 1494944 <1494944@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

Public bug reported:

WebFrame ownership has never been right. WebFrame's are created and
owned by Oxide but the current ownership has OxideQQuickWebFrame owning
the internal WebFrame classes, which leads to weird things like
WebFrame::Delete.

** Affects: oxide
     Importance: Low
         Status: Triaged

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

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

-- 
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/1494944

Title:
  oxide::WebFrame should own OxideQQuickWebFrame (not the other way
  around)

Status in Oxide:
  Triaged

Bug description:
  WebFrame ownership has never been right. WebFrame's are created and
  owned by Oxide but the current ownership has OxideQQuickWebFrame
  owning the internal WebFrame classes, which leads to weird things like
  WebFrame::Delete.

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