"John J. Foerch" <[email protected]> writes:
> On Wed, Aug 18, 2010 at 01:54:43PM +0200, Vitaly S. wrote:
>>
>> Dear Developers,
>>
>> First, open.window does not honor
>> browser_default_open_target=OPEN_NEW_BUFFER.
>> Second, the interaction in the newly opened window is not conkeror like, no
>> bindings not minibuffer.
>>
>> Here the test code:
>>
>> function test(I){
>> I.window.open("http://www.google.com";)
>> };
>> interactive("test", "blabla", test);
>>
>> Thanks
>> Vitally.
>
>
I have the most updated version, ran through:
git fetch
git merge origin
as indicated on install page.
>
> The answer to problem #1 is that browser_default_open_target only affects
> window.open calls from content js, not calls from chrome js. Interactive
> commands run in chrome js. You can test as follows:
>
> * make a file called a.html with the following contents:
>
> <html>
> <span onclick="window.open('http://example.com');">click me</span>
> </html>
>
> * run: conkeror -e 'browser_default_open_target=OPEN_NEW_BUFFER'
> `pwd`/window-open-bug.html
>
> * click the link
And how can I open the link in a new buffer from chrome js, then?
I usually navigate with negative mode enabled for the conkeror window (very
dark) and when a new
window pops up it just blinds me.
Tahaks.
_______________________________________________
Conkeror mailing list
[email protected]
https://www.mozdev.org/mailman/listinfo/conkeror
