WebView.navigationRequested isn't emitted for new-window navigations when WebView.newViewRequested isn't implemented

Bug #1302740 reported by Chris Coulson on 2014-04-04
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Oxide
Low
Chris Coulson

Bug Description

When WebView.newViewRequested isn't implemented, all navigations and window open requests are done in the current view. However, sites can navigate the current view with window.open() or a link with target="_blank" without WebView.navigationRequested being emitted

Chris Coulson (chrisccoulson) wrote :

Note, the same occurs for subframes too (except window.open() in a subframe will navigate the main frame if WebView.newViewRequested isn't implemented)

Changed in oxide:
status: New → Triaged
importance: Undecided → Medium
Chris Coulson (chrisccoulson) wrote :

The issue here is that delegating navigations to the browser behaves differently depending on whether the window has an opener or not (I'm not sure why). If a window doesn't have an opener, we get all top-level navigations. If it does have an opener, then we only get cross-domain navigations. When calling window.open() without support for creating new windows, blink sets window.opener on the top-level window (like it would for a newly created window) before calling in to content.

Changed in oxide:
importance: Medium → Low
Chris Coulson (chrisccoulson) wrote :

The fix for bug 1470268 will most likely resolve this

Changed in oxide:
assignee: nobody → Chris Coulson (chrisccoulson)
milestone: none → branch-1.11
assignee: Chris Coulson (chrisccoulson) → nobody
status: Triaged → In Progress
Changed in oxide:
status: In Progress → Fix Released
assignee: nobody → Chris Coulson (chrisccoulson)
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers