dwb - a webkit web browser

mhertz · 2012-01-07 23:49:45

.. Yes(to the above), and I also am not "remembered" anymore on gmail and here on the arch-forum, so I have to re-login upon new visits...

Edit: I'm sorry! I've just seen that somehow I had cookie-policy set as session and not persistent, and when setting it as persistent then everything is fine again... I've never changed that option(and just have changed the cookies option to always along time ago, so I don't get it, but oh well...

Edit2: Hmm, I swear that it first didn't worked, and i've tried many times, and then after changing the policy to persistant, then it began to work again, but now when I set it back to session, then it still works? Anyway sorry for posting useless bug-reports again!

Last edited by mhertz (2012-01-08 00:08:09)

portix · 2012-01-08 10:15:14

Fixed with revision 929:2d6b8c820f04.

portix · 2012-01-08 10:27:53

mhertz wrote:

.. Yes(to the above), and I also am not "remembered" anymore on gmail and here on the arch-forum, so I have to re-login upon new visits...
Edit: I'm sorry! I've just seen that somehow I had cookie-policy set as session and not persistent, and when setting it as persistent then everything is fine again... I've never changed that option(and just have changed the cookies option to always along time ago, so I don't get it, but oh well...
Edit2: Hmm, I swear that it first didn't worked, and i've tried many times, and then after changing the policy to persistant, then it began to work again, but now when I set it back to session, then it still works? Anyway sorry for posting useless bug-reports again!

I should document the new cookie settings. cookie-store-policy 'session' means that all session cookies are allowed but no cookie will be saved, except it is on the cookie.allow whitelist, to allow persistent cookies 'CC' can be used.
When cookie-store-policy is set to persistent all cookies are saved, so if you switch back to session there will be still the saved cookie that was saved when you used 'persistent'. I haven't decided yet if i will make it possible to delete cookies manually or if the cookies will be automatically removed if the cookie policy changes.
If the cookie-store-policy is set to 'never' all cookies are rejected only cookies on the cookies.allow whitelist are stored persitent and cookies on 'cookies_session.allow' are allowed for a session. The shortcut 'CS' can be used to put domains on the session whitelist. There is also now the shortcut 'CT' that allows all firstparty cookies just for the current session but does not save any domain on a whitelist or save any cookie.

mhertz · 2012-01-08 15:31:19

Ahh, thanks for the explenation, mate!

Could you please tell me what you mean by only dropping tilling mostly in contrary to fully? I mean, what, if any, tiling will then be left?

Also, why did you decide to ditch most tiling? Is it because you never use it yourself anymore?

I never use tiling in dwb myself, so actually welcome that change, but am just curious about what made you change such a "big" thing i.e. removing the "dynamic" part of dwb...

I'm just really curious about this...

Thanks in advance!

Last edited by mhertz (2012-01-08 15:37:39)

portix · 2012-01-08 15:41:16

I never used it and it seemed to me that no one ever used it. The only thing that is left is one could toggle the visibility of a tab. If more than 1 tab is visible all visible tabs and the active tab are shown side by side with equal width. This is much simpler (5 lines of code compared to 400 with the old tiling approach) and i find it more useful.

Trilby · 2012-01-08 16:21:50

After recent updates - and based on recent discussion - it seems the handling of cookies has changed.

I've had a bit of trouble getting dwb working well for me now. I prefer persistent cookies for many sites, such as this bbs so I do not have to log in every time I open dwb. It seems I need to have all cookies persistent now to get this to work - but I'd prefer not to have all sites' cookies be persistent.

I have read up on the cookie whitelist, but I can't get it to work for me. Manually editing the "cookies.allow" file does not seem to have an effect - perhaps I am missing an important part of what should be listed - I just put the bare domain name ("archlinux.org" and "bbs.archlinux.org"). I tried having dwb whitelist the domain by using the default keymap "CC", but every time I try this dwb seg-faults and closes. When run from a terminal I see the following:

** (dwb:14217): CRITICAL **: domain_get_base_for_host: assertion `_tld_table != NULL' failed
Received SIGSEGV, trying to clean up.

Am I doing something wrong? Is other information needed to diagnose this issue?

portix · 2012-01-08 16:30:31

You get exactly the old behaviour if you set the cookie-store-policy to session and the cookie-accept-policy to always, but cookie-accept-policy may be removed before the next release. The segfault has been fixed in tip.

Edit: On most sites it will be better pressing CC after you logged in, dwb always saves the last cookies and will whitelist the domains based on these cookies. You will be asked for each domain if you want to put it on the whitelist. If you press CC before logging in you will be asked only for first party domains (this doesn't work on all sites, e.g. gmail also sets third party cookies and it won't work without thirdparty cookies).

Last edited by portix (2012-01-08 16:51:57)

mhertz · 2012-01-08 17:19:36

Thanks alot for the explanation portix!

bloom · 2012-01-08 17:55:08

If I browse to:

http://browse.deviantart.com/?order=5&q=foo

Hitting 'f' will generate some hinting tags of the form '<valid_letter>undefined'.

My hint-letter-seq is:

asdfghjkl;

(It seems there's not enough digraphs to encompass all the links...)

Last edited by bloom (2012-01-08 17:58:32)

bloom · 2012-01-08 20:16:20

It seems 'B' (open_quickmark_nv) doesn't honor the 'background-tabs' setting (I've set it to 'true').

EDIT: sorry, in fact I like that behavior and I think it behaves ok in the over cases.

Also: shouldn't 'view' be replaced by 'tab' in the manual and everywhere else?

Last edited by bloom (2012-01-08 21:00:14)

Trilby · 2012-01-08 20:30:58

Ah, "CC" for cookies works perfectly now. Thanks.

portix · 2012-01-09 00:05:08

bloom wrote:

Hitting 'f' will generate some hinting tags of the form '<valid_letter>undefined'.

Now also shorter lettersequences should work.

bloom wrote:

Also: shouldn't 'view' be replaced by 'tab' in the manual and everywhere else?

Yes, i will update it when i update the whole manpage.

LighthouseKeeper · 2012-01-09 05:10:49

dwb is by far my favorite browser these days. Much thanks to you for this, portix.

My only area of difficulty is with the adblocker. I'm using the most recent version of dwb-hg with the unmodified text from easylist as my adblock filterlist. I have adblocking enabled and the correct path pointed to in settings, but nothing seems to get blocked. Any idea what I'm doing wrong? Thanks.

portix · 2012-01-09 09:06:32

LighthouseKeeper wrote:

dwb is by far my favorite browser these days. Much thanks to you for this, portix.
My only area of difficulty is with the adblocker. I'm using the most recent version of dwb-hg with the unmodified text from easylist as my adblock filterlist. I have adblocking enabled and the correct path pointed to in settings, but nothing seems to get blocked. Any idea what I'm doing wrong? Thanks.

Are there any warnings when you start dwb from commandline?

LighthouseKeeper · 2012-01-09 09:18:29

portix wrote:

Are there any warnings when you start dwb from commandline?

I got a few warnings along the lines of "Cannot open ~/.config/dwb/default/custom_keys: file not found," but nothing regarding the adblocker. I created all the missing files in my .config directory and now it launches with no warnings.

portix · 2012-01-09 10:09:08

LighthouseKeeper wrote:

portix wrote:
Are there any warnings when you start dwb from commandline?
I got a few warnings along the lines of "Cannot open ~/.config/dwb/default/custom_keys: file not found," but nothing regarding the adblocker. I created all the missing files in my .config directory and now it launches with no warnings.

Ok, it's my fault, it is now fixed in tip. You can also use the grab_adblocker-script which removes not supported filters from the filterlist, just uncomment the filterlists you want to use.
The warnings about missing files can be ignored if you don't use them.

Last edited by portix (2012-01-09 10:11:17)

Chase · 2012-01-09 19:33:50

This is an amazing piece of work! It's quickly becoming my default browser.

One question: Is there a way to open a link in a new tab while keeping focus on the current tab? Sorry if I overlooked it. It's just about the only thing from Firefox that I miss.

Incidentally, I whipped up this little script to open the bookmarks file with zenity, select a link, and open it with dwb. I execute it with a keyboard command in openbox.

#!/bin/bash

SRC=~/.config/dwb/default/bookmarks

if [ ! -r "$SRC" ]; then
  zenity --error --title=bookmarks --text="Missing $SRC"
  exit 1
fi

# The 'sed' command below converts the first space on each line of
# $SRC into a tab. Having changed $IFS, these tabs then serve as
# column separators in $ARR.

SAVEIFS=$IFS
IFS=$(echo -e "\n\t")
ARR=(`sed 's/ /\t/' $SRC`)
IFS=$SAVEIFS

# The 'zenity' command below hides the first column, containing URIs,
# so that the list contains only their names or descriptions.
# Double-clicking an item opens the corresponding site in dwb.

URL="`zenity --title="bookmarks" --list --column=Bookmarks --column=Names --hide-column=1 --hide-header --text="Please select a location." --height=400 --width=520 "${ARR[@]}"`"

if [ -n "$URL" ] && [ "$?" = "0" ]; then
  dwb $URL
fi

exit 0

There's probably a better way of doing this. But it works for me.

LighthouseKeeper · 2012-01-09 19:52:55

@Chase - I think it's just a matter of enabling 'background-tabs.'

@Portix - running the script seems to have done the trick, thanks. Maybe the comments and unsupported rules in my unmodified easylist text were making the whole thing unusable?

portix · 2012-01-09 20:08:12

LightHouseKeeper wrote:

@Portix - running the script seems to have done the trick, thanks. Maybe the comments and unsupported rules in my unmodified easylist text were making the whole thing unusable?

No, there was a bug that is fixed now. The adblocker works also with comments and unsupported rules but dwb will warn about unsupported rules so using the script is recommended.

Chase wrote:

One question: Is there a way to open a link in a new tab while keeping focus on the current tab? Sorry if I overlooked it. It's just about the only thing from Firefox that I miss.

If you open a new tab from commandline it is not possible. I never use background tabs and i don't know what the common behaviour of background tabs is, but for opening tabs from commandline it seems reasonable to open them in background if background-tabs are enabled, so maybe i will change this.

bloom · 2012-01-09 20:28:00

portix wrote:

bloom wrote:
Hitting 'f' will generate some hinting tags of the form '<valid_letter>undefined'.
Now also shorter lettersequences should work.

I works very well indeed.

I've applied the diff of this commit:
https://bitbucket.org/portix/dwb/changeset/446e9ddbc28c

And now, the Insert mode behaves as expected, thanks!
(The only problem I've noticed so far is that '<space>' is no longer the equivalent of 'C-f' in Normal mode but it is in Insert mode.)

I'm missing a few standard UNIX shortcuts in the input bar: 'C-g' should be equivalent to '<esc>' and 'C-j' should be equivalent to '<return>'.

Last edited by bloom (2012-01-09 20:36:22)

portix · 2012-01-09 20:49:38

bloom wrote:

I've applied the diff of this commit:
https://bitbucket.org/portix/dwb/changeset/446e9ddbc28c
And now, the Insert mode behaves as expected.
(The only problem I've noticed so far is that '<space>' is no longer the equivalent of 'C-f' in Normal mode but it is in Insert mode.)

And now i remember why unbound keys were inserted in textinputs/textareas even in normal mode. But it should be easily possible to have both, text not getting inserted in inputs and having the default webkit builtin shortcuts enabled.

bloom · 2012-01-09 20:58:18

portix wrote:

bloom wrote:
I've applied the diff of this commit:
https://bitbucket.org/portix/dwb/changeset/446e9ddbc28c
And now, the Insert mode behaves as expected.
(The only problem I've noticed so far is that '<space>' is no longer the equivalent of 'C-f' in Normal mode but it is in Insert mode.)
And now i remember why unbound keys were inserted in textinputs/textareas even in normal mode. But it should be easily possible to have both, text not getting inserted in inputs and having the default webkit builtin shortcuts enabled.

As a temporary fix, I've added a custom command:

space:scroll_page_down

But I'm not sure on how to bind 'Shift-space' to 'scroll_page_up' (I think the shortcut component should be 'backspace')?

Last edited by bloom (2012-01-09 21:07:30)

portix · 2012-01-09 21:18:30

bloom wrote:

But I'm not sure on how to bind 'Shift-space' to 'scroll_page_up'?

There was a check for modifier keys missing in new custom command code which should be fixed now, you can bind it with

Shift space: scroll_page_up

However the code you merged manually will be merged to the default branch in a few days, i already modified it so that the webkit builtin shortcuts aren't ignored.

Edit: Also the syntax for non printing keys will change in a few days, non printing keys like space must then be encapsulated in @, so you have to change it to

Shift @space@

then.

Last edited by portix (2012-01-09 21:44:16)

Chase · 2012-01-09 23:43:04

portix wrote:

If you open a new tab from commandline it is not possible.

Thanks for responding. I was thinking of when I right-click on a link and select "Open Link in a New Window". The browser switches focus from the current tab to the new one. I have "background-tabs" set, as LighthouseKeeper suggested, but although that works when using the keyboard to follow hints, it doesn't affect the behavior of the context menu.

As for opening new tabs from the commandline, the current behavior seems right. I'd expect that tab to get the focus, so I'm glad that it does!

portix · 2012-01-09 23:51:47

Chase wrote:

Thanks for responding. I was thinking of when I right-click on a link and select "Open Link in a New Window". The browser switches focus from the current tab to the new one. I have "background-tabs" set, as LighthouseKeeper suggested, but although that works when using the keyboard to follow hints, it doesn't affect the behavior of the context menu.

You're right, i will change this soon, at the latest when the current experimental branch is merged into the default branch.

Last edited by portix (2012-01-10 09:36:22)

Arch Linux

#451 2012-01-07 23:49:45

Re: dwb - a webkit web browser

#452 2012-01-08 10:15:14

Re: dwb - a webkit web browser

#453 2012-01-08 10:27:53

Re: dwb - a webkit web browser

#454 2012-01-08 15:31:19

Re: dwb - a webkit web browser

#455 2012-01-08 15:41:16

Re: dwb - a webkit web browser

#456 2012-01-08 16:21:50

Re: dwb - a webkit web browser

#457 2012-01-08 16:30:31

Re: dwb - a webkit web browser

#458 2012-01-08 17:19:36

Re: dwb - a webkit web browser

#459 2012-01-08 17:55:08

Re: dwb - a webkit web browser

#460 2012-01-08 20:16:20

Re: dwb - a webkit web browser

#461 2012-01-08 20:30:58

Re: dwb - a webkit web browser

#462 2012-01-09 00:05:08

Re: dwb - a webkit web browser

#463 2012-01-09 05:10:49

Re: dwb - a webkit web browser

#464 2012-01-09 09:06:32

Re: dwb - a webkit web browser

#465 2012-01-09 09:18:29

Re: dwb - a webkit web browser

#466 2012-01-09 10:09:08

Re: dwb - a webkit web browser

#467 2012-01-09 19:33:50

Re: dwb - a webkit web browser

#468 2012-01-09 19:52:55

Re: dwb - a webkit web browser

#469 2012-01-09 20:08:12

Re: dwb - a webkit web browser

#470 2012-01-09 20:28:00

Re: dwb - a webkit web browser

#471 2012-01-09 20:49:38

Re: dwb - a webkit web browser

#472 2012-01-09 20:58:18

Re: dwb - a webkit web browser

#473 2012-01-09 21:18:30

Re: dwb - a webkit web browser

#474 2012-01-09 23:43:04

Re: dwb - a webkit web browser

#475 2012-01-09 23:51:47

Re: dwb - a webkit web browser

Board footer