[Webkit-unassigned] [Bug 23932] Current API does not allow us to open target="_blank" links in new tabs instead of windows

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=23932





------- Comment #12 from xan.lopez at gmail.com  2009-03-24 13:04 PDT -------
(In reply to comment #11)
> (In reply to comment #8)
> > Keep in mind that create-web-view is much more generic than this, and does not
> > include neither a 'reason' (like 'link clicked') or state/button information.
> > This signal overlaps a lot with navigation-action, but the problem with that
> > one signal is that it won't include any metadata (reason, state, button, ...)
> > for, at least, target=_blank links. I suggested fixing that, but various Apple
> > developers told me this was by design.
> 
> Actually navigation-policy-decision-requested won't be emitted at all for
> target=_blank links, and as you point out, create-web-view doesn't have enough
> information. So we either need a new signal like it's done here, or implement
> the missing cases in the current signals (I'd prefer the later i.e. having one
> signal for all the "user clicks on a link" cases, but if that's not wanted due
> to the design, this is OK).
> 

navigation-policy-decision-requested *is* emitted, but it lacks the information
to do certain things, like open them in a new tab, as commented in the bug. The
signal doc in alex's comment is pretty accurate AFAIK, and I think is the best
solution, because "fixing" the navigation-policy action is not an option (ie,
there's nothing wrong with it, it's just that webkit gives you a lot of details
about what's going on in the browser, not just one-fits-all signal).


-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.