Oxide

OxideQCertificateError::isMainFrame will not work properly with Chromium 49

Bug #1520189 reported by Chris Coulson
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Oxide
Fix Released
Medium
Chris Coulson
Oxide branch-1.13

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).

Chris Coulson (chrisccoulson)
Changed in oxide:
milestone: none → branch-1.13
importance: Undecided → Medium
status: New → Triaged
Chris Coulson (chrisccoulson)
Changed in oxide:
assignee: nobody → Chris Coulson (chrisccoulson)
Chris Coulson (chrisccoulson)
Changed in oxide:
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.