ubuntu-webapps-bugs team mailing list archive

[Chris Coulson <chris.coulson@xxxxxxxxxxxxx>]

Public bug reported:

OxideQNetworkCallbackEvent has a property called isMainFrame for
determining if the request originated from a main frame or not. However,
I can't think of any case when this would be useful on its own - the
most common case for using this property would be to determine if the
request is for the main document load in the main frame. For this, it
needs to either expose the resource type or add another property,
"isSubresource".

** Affects: oxide
     Importance: Low
         Status: Triaged

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

** 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/1444621

Title:
  OxideQNetworkCallbackEvent::isMainFrame is quite useless on its own

Status in Oxide Webview:
  Triaged

Bug description:
  OxideQNetworkCallbackEvent has a property called isMainFrame for
  determining if the request originated from a main frame or not.
  However, I can't think of any case when this would be useful on its
  own - the most common case for using this property would be to
  determine if the request is for the main document load in the main
  frame. For this, it needs to either expose the resource type or add
  another property, "isSubresource".

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