[Conkeror] open_newwindow prefs have no effect
Jeremy Maitin-Shepard
jeremy at jeremyms.com
Tue Jul 8 22:42:56 PDT 2008
Decklin Foster <decklin at red-bean.com> writes:
> I'm trying to set up Conkeror to open links appropriately. This is the
> policy I want when following links:
> - I *always* decide whether to open a new buffer or not
> - Web pages *never* decide whether I open a new buffer or not.
> In Firefox I set browser.link.open_newwindow to 1 and
> browser.link.open_newwindow.restriction to 0. Adjusting these preferences
> seems to have no effect in Conkeror.
You shouldn't use these preferences. Instead, you can use the variable
browser_default_open_target to customize the target a little bit. That
doesn't really do what you want. If JavaScript is being used, it is not
always possible for Conkeror to force either that the target be opened
in the current buffer (or current frame) or that it be opened in a new
buffer. Currently, it would be possible to force that it open in the
current buffer or frame in the case that JavaScript requests a new
window, but if JavaScript opens the target in an existing frame, there
is no simple way to override that and force it to open in a new frame.
> Is this a known issue? Is there something I can do to fix it? Or should
> I be setting this in another way?
--
Jeremy Maitin-Shepard
More information about the Conkeror
mailing list