dwb - a webkit web browser

sardina · 2013-07-31 18:55:16

Guys, do you know how to add exceptions to adblock in dwb?

I suppose one has to edit 'adblock_default', but how?

In my case, I want to add soundcloud.com.

portix · 2013-08-01 12:01:08

sardina wrote:

Guys, do you know how to add exceptions to adblock in dwb?
I suppose one has to edit 'adblock_default', but how?
In my case, I want to add soundcloud.com.

Currently there is no way to add exceptions.

F34R · 2013-08-04 12:01:46

Another issue for me , search picture in google and scroll medium-fast high cpu usage in one core , click and view where is the picture homepage some seconds freez.
Try other webkit browser , luakit use the chrome user agent and the google appearance similar like some years ago before. (in picture search not included black g+ preview and others)

Ambrevar · 2013-08-04 17:38:29

There is one issue with the navigation history that has been bugging me for some time: tabopen will save an empty entry in the navigate.history file (you can check this while dwb is running).

For instance enter the following (o is the :open binding, O the :tabopen binding)
* o dummy1
* O dummy2
* o dummy3
* o C-k C-k C-k
this will output

dummy3
dummy3
dummy1

The O binding used to work well a few months ago.
I did a bisect, and found out the bug first appeared at commit 6c1d083ff8de9d79c79f1f16e8c2cf951832cda0.

I've already filed an issue at the bugtracker several weeks ago (https://bitbucket.org/portix/dwb/issue/ … er-tabopen), but portix said he couldn't reproduce this. So I'm posting here to know if other dwb users have the same issue.

Note that I did test this on a vanilla build with no user configuration.

z1lt0id · 2013-08-06 13:54:02

I know I've mentioned this before but with the current git of dwb I've noticed that it segfault when click on comments at Google+. On the down arrow and now if you click for example "2 comments"

Last 87 stack frames: 

 87: dwb() [0x410b70]
 86: dwb() [0x42b0bf]
 85: /usr/lib64/libc.so.6(+0x35240) [0x7f9802135240]
 84: /usr/lib64/libwebkitgtk-1.0.so.0(+0xad1e0c) [0x7f9805a69e0c]
 83: /usr/lib64/libwebkitgtk-1.0.so.0(+0xad2508) [0x7f9805a6a508]
 82: /usr/lib64/libwebkitgtk-1.0.so.0(+0xad3623) [0x7f9805a6b623]
 81: /usr/lib64/libwebkitgtk-1.0.so.0(+0xab96f3) [0x7f9805a516f3]
 80: /usr/lib64/libwebkitgtk-1.0.so.0(+0xad1c23) [0x7f9805a69c23]
 79: /usr/lib64/libwebkitgtk-1.0.so.0(+0xad2508) [0x7f9805a6a508]
 78: /usr/lib64/libwebkitgtk-1.0.so.0(+0xad3623) [0x7f9805a6b623]
 77: /usr/lib64/libwebkitgtk-1.0.so.0(+0xab96f3) [0x7f9805a516f3]
 76: /usr/lib64/libwebkitgtk-1.0.so.0(+0xad1c23) [0x7f9805a69c23]
 75: /usr/lib64/libwebkitgtk-1.0.so.0(+0xad2508) [0x7f9805a6a508]
 74: /usr/lib64/libwebkitgtk-1.0.so.0(+0xad3623) [0x7f9805a6b623]
 73: /usr/lib64/libwebkitgtk-1.0.so.0(+0xab96f3) [0x7f9805a516f3]
 72: /usr/lib64/libwebkitgtk-1.0.so.0(+0xad1c23) [0x7f9805a69c23]
 71: /usr/lib64/libwebkitgtk-1.0.so.0(+0xad2508) [0x7f9805a6a508]
 70: /usr/lib64/libwebkitgtk-1.0.so.0(+0xad3623) [0x7f9805a6b623]
 69: /usr/lib64/libwebkitgtk-1.0.so.0(+0xab96f3) [0x7f9805a516f3]
 68: /usr/lib64/libwebkitgtk-1.0.so.0(+0xad1c23) [0x7f9805a69c23]
 67: /usr/lib64/libwebkitgtk-1.0.so.0(+0xad2508) [0x7f9805a6a508]
 66: /usr/lib64/libwebkitgtk-1.0.so.0(+0xad3623) [0x7f9805a6b623]
 65: /usr/lib64/libwebkitgtk-1.0.so.0(+0xab96f3) [0x7f9805a516f3]
 64: /usr/lib64/libwebkitgtk-1.0.so.0(+0xad1c23) [0x7f9805a69c23]
 63: /usr/lib64/libwebkitgtk-1.0.so.0(+0xad2508) [0x7f9805a6a508]
 62: /usr/lib64/libwebkitgtk-1.0.so.0(+0xad3623) [0x7f9805a6b623]
 61: /usr/lib64/libwebkitgtk-1.0.so.0(+0xab96f3) [0x7f9805a516f3]
 60: /usr/lib64/libwebkitgtk-1.0.so.0(+0xaec304) [0x7f9805a84304]
 59: /usr/lib64/libwebkitgtk-1.0.so.0(+0xad3368) [0x7f9805a6b368]
 58: /usr/lib64/libwebkitgtk-1.0.so.0(+0xab96f3) [0x7f9805a516f3]
 57: /usr/lib64/libwebkitgtk-1.0.so.0(+0xad1c23) [0x7f9805a69c23]
 56: /usr/lib64/libwebkitgtk-1.0.so.0(+0xad2508) [0x7f9805a6a508]
 55: /usr/lib64/libwebkitgtk-1.0.so.0(+0xad3623) [0x7f9805a6b623]
 54: /usr/lib64/libwebkitgtk-1.0.so.0(+0xab96f3) [0x7f9805a516f3]
 53: /usr/lib64/libwebkitgtk-1.0.so.0(+0xad1c23) [0x7f9805a69c23]
 52: /usr/lib64/libwebkitgtk-1.0.so.0(+0xad2508) [0x7f9805a6a508]
 51: /usr/lib64/libwebkitgtk-1.0.so.0(+0xad3623) [0x7f9805a6b623]
 50: /usr/lib64/libwebkitgtk-1.0.so.0(+0xbac918) [0x7f9805b44918]
 49: /usr/lib64/libwebkitgtk-1.0.so.0(+0xbb8f2c) [0x7f9805b50f2c]
 48: /usr/lib64/libwebkitgtk-1.0.so.0(+0xbbd9ec) [0x7f9805b559ec]
 47: /usr/lib64/libwebkitgtk-1.0.so.0(+0xbb666d) [0x7f9805b4e66d]
 46: /usr/lib64/libwebkitgtk-1.0.so.0(+0xad1c23) [0x7f9805a69c23]
 45: /usr/lib64/libwebkitgtk-1.0.so.0(+0xad2508) [0x7f9805a6a508]
 44: /usr/lib64/libwebkitgtk-1.0.so.0(+0xad3623) [0x7f9805a6b623]
 43: /usr/lib64/libwebkitgtk-1.0.so.0(+0xab96f3) [0x7f9805a516f3]
 42: /usr/lib64/libwebkitgtk-1.0.so.0(+0xad1c23) [0x7f9805a69c23]
 41: /usr/lib64/libwebkitgtk-1.0.so.0(+0xad2508) [0x7f9805a6a508]
 40: /usr/lib64/libwebkitgtk-1.0.so.0(+0xad3623) [0x7f9805a6b623]
 39: /usr/lib64/libwebkitgtk-1.0.so.0(+0xab96f3) [0x7f9805a516f3]
 38: /usr/lib64/libwebkitgtk-1.0.so.0(+0xad1c23) [0x7f9805a69c23]
 37: /usr/lib64/libwebkitgtk-1.0.so.0(+0xad2508) [0x7f9805a6a508]
 36: /usr/lib64/libwebkitgtk-1.0.so.0(+0xad3623) [0x7f9805a6b623]
 35: /usr/lib64/libwebkitgtk-1.0.so.0(+0xab96f3) [0x7f9805a516f3]
 34: /usr/lib64/libwebkitgtk-1.0.so.0(+0xad1c23) [0x7f9805a69c23]
 33: /usr/lib64/libwebkitgtk-1.0.so.0(+0xad2508) [0x7f9805a6a508]
 32: /usr/lib64/libwebkitgtk-1.0.so.0(+0xad3623) [0x7f9805a6b623]
 31: /usr/lib64/libwebkitgtk-1.0.so.0(+0xab96f3) [0x7f9805a516f3]
 30: /usr/lib64/libwebkitgtk-1.0.so.0(+0xad1c23) [0x7f9805a69c23]
 29: /usr/lib64/libwebkitgtk-1.0.so.0(+0xad2508) [0x7f9805a6a508]
 28: /usr/lib64/libwebkitgtk-1.0.so.0(+0xad3623) [0x7f9805a6b623]
 27: /usr/lib64/libwebkitgtk-1.0.so.0(+0xab96f3) [0x7f9805a516f3]
 26: /usr/lib64/libwebkitgtk-1.0.so.0(+0xad1c23) [0x7f9805a69c23]
 25: /usr/lib64/libwebkitgtk-1.0.so.0(+0xad2508) [0x7f9805a6a508]
 24: /usr/lib64/libwebkitgtk-1.0.so.0(+0xad3623) [0x7f9805a6b623]
 23: /usr/lib64/libwebkitgtk-1.0.so.0(+0xab96f3) [0x7f9805a516f3]
 22: /usr/lib64/libwebkitgtk-1.0.so.0(+0xad1c23) [0x7f9805a69c23]
 21: /usr/lib64/libwebkitgtk-1.0.so.0(+0xad2508) [0x7f9805a6a508]
 20: /usr/lib64/libwebkitgtk-1.0.so.0(+0xad3623) [0x7f9805a6b623]
 19: /usr/lib64/libwebkitgtk-1.0.so.0(+0xab96f3) [0x7f9805a516f3]
 18: /usr/lib64/libwebkitgtk-1.0.so.0(+0xad1c23) [0x7f9805a69c23]
 17: /usr/lib64/libwebkitgtk-1.0.so.0(+0xad2508) [0x7f9805a6a508]
 16: /usr/lib64/libwebkitgtk-1.0.so.0(+0xad3623) [0x7f9805a6b623]
 15: /usr/lib64/libwebkitgtk-1.0.so.0(+0xab96f3) [0x7f9805a516f3]
 14: /usr/lib64/libwebkitgtk-1.0.so.0(+0xac722f) [0x7f9805a5f22f]
 13: /usr/lib64/libwebkitgtk-1.0.so.0(+0xad3022) [0x7f9805a6b022]
 12: /usr/lib64/libwebkitgtk-1.0.so.0(+0xad35d8) [0x7f9805a6b5d8]
 11: /usr/lib64/libwebkitgtk-1.0.so.0(+0xab96f3) [0x7f9805a516f3]
 10: /usr/lib64/libwebkitgtk-1.0.so.0(+0xbe1c78) [0x7f9805b79c78]
  9: /usr/lib64/libwebkitgtk-1.0.so.0(+0xa5e9ed) [0x7f98059f69ed]
  8: /usr/lib64/libwebkitgtk-1.0.so.0(_ZN7WebCore8Document36updateLayoutIgnorePendingStylesheetsEv+0x4f) [0x7f980562e11f]
  7: /usr/lib64/libwebkitgtk-1.0.so.0(+0x6aafc4) [0x7f9805642fc4]
  6: /usr/lib64/libwebkitgtk-1.0.so.0(+0xdbd71c) [0x7f9805d5571c]
  5: /usr/lib64/libwebkitgtk-1.0.so.0(+0xdc0c7c) [0x7f9805d58c7c]
  4: /usr/lib64/libwebkitgtk-1.0.so.0(+0xe28609) [0x7f9805dc0609]
  3: /usr/lib64/libwebkitgtk-1.0.so.0(+0xe208d9) [0x7f9805db88d9]
  2: /usr/lib64/libjavascriptcoregtk-1.0.so.0(+0x24542f) [0x7f980326d42f]
  1: /usr/lib64/libjavascriptcoregtk-1.0.so.0(+0x24e1c9) [0x7f98032761c9]
Segmentation fault (core dumped)

EDIT: I noticed this bug isn't in the dwb-gtk3 version though.

Last edited by z1lt0id (2013-08-06 14:04:40)

portix · 2013-08-06 15:28:57

Could you create a ticket on the bugtracker and append a backtrace, if you don't know how to create a backtrace, there is a script that creates a backtrace, you only need gdb installed.

NeanderMarcl · 2013-08-06 19:11:10

Hi,

I've reinstall Arch, and when I go to htlm5.grooveshark and vimeo by using the awesome dwb it don't have sound
In the vimeo website, Oops...
Gstreamer is installed.
How can I fix it please ?

Last edited by NeanderMarcl (2013-08-06 19:11:37)

NeanderMarcl · 2013-08-06 21:04:31

I missed a paquet not present in the wiki.
Fix it by installing the gstreamer-ffmpeg

karol · 2013-08-06 21:09:41

NeanderMarcl wrote:

I missed a paquet not present in the wiki.
Fix it by installing the gstreamer-ffmpeg

I think you mean gstreamer0.10-ffmpeg.

WonderWoofy · 2013-08-06 21:48:06

karol wrote:

NeanderMarcl wrote:
I missed a paquet not present in the wiki.
Fix it by installing the gstreamer-ffmpeg
I think you mean gstreamer0.10-ffmpeg.

I think that depends on whether the OP is using dwb (gtk2) or dwb-gtk3. Webkitgtk (which is webkitgtk3) depends on gst-plugins-base-libs while webkitgtk2 depends on gstreamer0.10-base.

serdotlinecho · 2013-08-07 05:51:07

Anyone using dark gtk2 theme? I'm using FlatStudioDark and have create customstylesheet.css in ~/.config/dwb/ to fix the black font color input and textarea on {wiki|bbs|aur}.archlinux.org. And this is my ccs script to match FlatStudioDark theme and I like this way:

body {
    background-color: #222;
}

/* @-moz-document regexp("(?!https?://www\.(google\.com|youtube\.com|facebook\.com)).*$") */
input, textarea {
    background-color: #2c2e2f !important;
    color: #bfb5b5 !important;
    padding: 2px; !important;
    border-color: #4d679a !important;
    border-radius: 2px !important;
    border: 2px solid;
}

.dwb_hint {
    background-color: #ffd76e !important; 
    color: #000000 !important; /* hint fg */
    border: 1px solid #000000 !important;
    padding-left: 2px !important; 
    padding-right: 2px !important;
    border-radius: 2px !important;
    font-family: "Droid Sans" bold !important;
    font-size: 7pt !important;
}

.dwb_overlay_normal {
	border: 2px solid #ffffff !important;
	background-color: rgba(255,0,0,0.0) !important; 
	color: #ffffff !important; /* overlay fg */
}

But this script make google,youtube,facebook search and text box use black background too. I try to add exception using "@-moz-document regexp", but when I uncomment this lines "@-moz-document regexp("(?!https?://www\.(google\.com|youtube\.com|facebook\.com)).*$")" and restart dwb, the font on wiki,bbs,aur archlinux.org turn to black again. If anyone have better ccs script, please do share it with me.

NeanderMarcl · 2013-08-07 07:52:47

karol wrote:

NeanderMarcl wrote:
I missed a paquet not present in the wiki.
Fix it by installing the gstreamer-ffmpeg
I think you mean gstreamer0.10-ffmpeg.

Yes.

NeanderMarcl · 2013-08-07 07:55:03

WonderWoofy wrote:

karol wrote:
NeanderMarcl wrote:
I missed a paquet not present in the wiki.
Fix it by installing the gstreamer-ffmpeg
I think you mean gstreamer0.10-ffmpeg.
I think that depends on whether the OP is using dwb (gtk2) or dwb-gtk3. Webkitgtk (which is webkitgtk3) depends on gst-plugins-base-libs while webkitgtk2 depends on gstreamer0.10-base.

I used dwb (gtk2).

nem · 2013-08-14 08:18:31

would it be possible to have privacy extensions like ghostery for ff or similar?

Trilby · 2013-08-14 13:00:00

Portix,

I'm curious if you've ever considered (or whether it'd even be possible) to use a different rendering backend such as Mozilla's Gecko in place of webkit.

Webkit just seems to be accumulating issues that are placed in the "will not solve" categroy by webkit developers. Most recently I've found that most of the web-based services of my university are now completely inaccessible via webkit browsers - and unfortunately I am required to regularly use many of these online tools. Several times I've considered trying my hand at writing a dwb/luakit-like browser based on Gecko, but I'm horrible with C++ and just out of my depth with most of it. I suppose I may have to set up vimperator/pentadactyl or some such at work for now. But if you've ever brainstormed on using a different backend, I'd love to hear your thoughts.

Last edited by Trilby (2013-08-14 13:00:42)

portix · 2013-08-14 13:23:32

I have already played with chromium embedded framework which will use blink in the future since it uses chromium as a backend. The main problem is that i would nearly need to write dwb from scratch and i currently don't have enough spare time.

Trilby · 2013-08-14 13:57:21

Thanks for the quick answer. I'll have to start learning about blink/chromium-embedded.

bohoomil · 2013-08-14 16:50:06

Trilby wrote:

Portix,
I'm curious if you've ever considered (or whether it'd even be possible) to use a different rendering backend such as Mozilla's Gecko in place of webkit.

+1 Mozilla's backend has been the only thing on my dwb wish list. I am aware of the fact that this may never happen, especially now that you have mentioned chromium embedded, but just in case you were planning some major changes one day in the future, please consider going this way. There aren't many lighweight alternatives to Firefox after all…

nfisher.sr · 2013-08-14 17:25:24

I'd seriously question whether Gecko can ever be as lightweight as Webkit, in any form.

I'm happy with Webkit for the most part. Web developers should be encouraged to fix their sites and not ask browsers to conform to -their- quirks, not the other way round. If there's an actual bug in the rendering engine that's another story, but I think most issues fall into the one category and not the other.

Trilby · 2013-08-14 17:34:51

There are many bugs in webkit (example, example). That's the problem. I have long been a fan of webkit, but I do see it going downhill fast.

Last edited by Trilby (2013-08-14 17:35:14)

Cloudef · 2013-08-14 17:45:35

I don't think there are any good web engines out there currently. All are bloated, buggy crap (expect for the primitive text ones).
It's not really their fault, but the really ridiculously increasing web standards, javascript and what not.

But yeah, webkit seems to be the one most crappy right now and it's dragging dwb's potential. I am currently hoping that servo will succeed.

Last edited by Cloudef (2013-08-14 17:46:23)

WonderWoofy · 2013-08-14 17:56:37

I have been using dwb exclusively since about Nov. 2012. My pacman log says that I installed it on 2012-10-25, and I remember taking a liking to it nearly immediately (coming from luakit). So it is with great sadness that I have to admit that yesterday, I installed pentadactyl and configured it to work as similarly to dwb as I can make it.

Portix, you have made an unbelieveably great browser, so thanks for that. Unfortunately Cloudef is right in saying that webkits current crappiness is "dragging dwb's potential".

nfisher.sr · 2013-08-14 18:20:27

Ah, I see the gist. Since I rarely have javascript turned on (why would I with only 512mB ram?) I hadn't seen how buggy it was getting in webkit. I see all of your points now. At the same time, every time a web developer writes more javascript code into a site I want to get out a paddle. Especially if they don't allow any access to the site's functionality without it. It's just inconsiderate. I personally liken javascript to flash. An (un)neccessary evil that somehow became a standard.

And now, off my soapbox.

WonderWoofy · 2013-08-14 18:23:21

I don't even have javascript enabled, and I still experiences these crashes sometimes. When I did have it enabled though it just got worse and worse and worse.

mwgkgk · 2013-08-15 08:51:54

To be fair, dwb still works just fine for my everyday tasks. For vulnerable operations, I open chromium / firefox.

For the pages that refuse to render correctly under dwb, I have 2 userscripts:

#!/bin/bash
# dwb: Control l

chromium --incognito $DWB_URI

and

#!/bin/bash
# dwb: Control o

firefox $DWB_URI

Of course, it'd be awesome to use dwb for everything, I hope one day I'll be able to do that :)

I indeed use vimperator (pentadactyl does not seem to support modern firefox versions) / vimium as well, but there are some limitations that browser addons face that can be fairly annoying. Like vimperator getting stuck on flash videos, or vimium / vrome not working on about:blank / google app pages.

To be fair, it'd be really cool if portix had time to rewrite dwb to use another engine. But for now, I use dwb anyway and have a lot of fun doing so!

Arch Linux

#1751 2013-07-31 18:55:16

Re: dwb - a webkit web browser

#1752 2013-08-01 12:01:08

Re: dwb - a webkit web browser

#1753 2013-08-04 12:01:46

Re: dwb - a webkit web browser

#1754 2013-08-04 17:38:29

Re: dwb - a webkit web browser

#1755 2013-08-06 13:54:02

Re: dwb - a webkit web browser

#1756 2013-08-06 15:28:57

Re: dwb - a webkit web browser

#1757 2013-08-06 19:11:10

Re: dwb - a webkit web browser

#1758 2013-08-06 21:04:31

Re: dwb - a webkit web browser

#1759 2013-08-06 21:09:41

Re: dwb - a webkit web browser

#1760 2013-08-06 21:48:06

Re: dwb - a webkit web browser

#1761 2013-08-07 05:51:07

Re: dwb - a webkit web browser

#1762 2013-08-07 07:52:47

Re: dwb - a webkit web browser

#1763 2013-08-07 07:55:03

Re: dwb - a webkit web browser

#1764 2013-08-14 08:18:31

Re: dwb - a webkit web browser

#1765 2013-08-14 13:00:00

Re: dwb - a webkit web browser

#1766 2013-08-14 13:23:32

Re: dwb - a webkit web browser

#1767 2013-08-14 13:57:21

Re: dwb - a webkit web browser

#1768 2013-08-14 16:50:06

Re: dwb - a webkit web browser

#1769 2013-08-14 17:25:24

Re: dwb - a webkit web browser

#1770 2013-08-14 17:34:51

Re: dwb - a webkit web browser

#1771 2013-08-14 17:45:35

Re: dwb - a webkit web browser

#1772 2013-08-14 17:56:37

Re: dwb - a webkit web browser

#1773 2013-08-14 18:20:27

Re: dwb - a webkit web browser

#1774 2013-08-14 18:23:21

Re: dwb - a webkit web browser

#1775 2013-08-15 08:51:54

Re: dwb - a webkit web browser

Board footer