ubuntu-webapps-bugs team mailing list archive

[Chris Coulson <chris.coulson@xxxxxxxxxxxxx>]

Public bug reported:

Since
https://chromium.googlesource.com/chromium/src.git/+/0d32d6d30fec43e2ad159193c65ace6636537b23,
we can no longer determine whether the error is for a subresource
request in the main frame, as we no longer have access to the
originating RenderFrameHost (because there will be no RFH with browser-
side navigations in some cases).

** Affects: oxide
     Importance: Medium
         Status: Triaged

** Changed in: oxide
    Milestone: None => branch-1.13

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

Title:
  OxideQCertificateError::isMainFrame will not work properly with
  Chromium 49

Status in Oxide:
  Triaged

Bug description:
  Since
  https://chromium.googlesource.com/chromium/src.git/+/0d32d6d30fec43e2ad159193c65ace6636537b23,
  we can no longer determine whether the error is for a subresource
  request in the main frame, as we no longer have access to the
  originating RenderFrameHost (because there will be no RFH with
  browser-side navigations in some cases).

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