![]() ![]() It wasn’t easy at all and it is still a PITA in some cases but if I had fixed it any other way I would get tons of different complains □ Anyway, if a page decides to set 1.0 we can’t do anything and we have to comply, which obviously can be a PITA if you put it together with the flat volumes feature of Pulseaudio. * HTML5 spec says that the default volume for a media element is 1.0 (100%) but the user agent (a.k.a.) the browser can keep the former volume (final solution we took). ![]() * We could add a GStreamer volume element to avoid the issue and we would loose any integration with GNOME regarding volume. * If that element is pulse, pulse can come with or without flat volumes. * WebKitGTK+ has to work with whichever GStreamer volume element is taken. You can read the whole discussion at, but I can summarize it as: Still not touched.Īh, the infamous volume bug! It took me a lot of discussion and try to find a solution that wouldn’t compromise all things that needed to be taken into account. Downloaded the packages, installed them and opened Epiphany. Yesterday I enabled the repository for Arch and, to my surprise, it already had the packages epiphany 3.18.0 & webkit2gtk 2.10.0-1. Epiphany’s keybindings override the page’s ones. ![]()
0 Comments
Leave a Reply. |