Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision |
midori:faq [2014/06/05 00:00] – [Getting started] rename section gue5t | midori:faq [2014/06/05 00:44] – mention about:version directly gue5t |
---|
| |
=== Scroll with middle mouse button/ pan-scrolling === | === Scroll with middle mouse button/ pan-scrolling === |
| |
| Windows-style middle-click behavior is |
| |
http://ubuntuforums.org/showthread.php?t=478418 | http://ubuntuforums.org/showthread.php?t=478418 |
Upstream Bug: https://bugs.webkit.org/show_bug.cgi?id=50561 | Upstream Bug: https://bugs.webkit.org/show_bug.cgi?id=50561 |
| |
=== HTML5 Video doesn't play === | === HTML5 Video/ Audio doesn't play === |
| |
You need to have GStreamer plugins installed which implement the codecs. | [[#midori_architecture|Midori uses GStreamer]] for HTML5 audio and video support. Codecs, which handle particular formats of audio or video, are provided by GStreamer plugins which may need to be installed separately. Midori may be built with GTK+2 or GTK+3 (visit about:version to check), which correspond to GStreamer versions of 0.10 or 1.0 respectively. |
| |
- You need gstreamer0.10-pulse if you're using PulseAudio. | - You need gstreamer(0.10/1.0)-pulse if you're using PulseAudio. |
- You may need gstreamer0.10-alsa for ALSA, depending on your distribution. | - You may need gstreamer(0.10/1.0)-alsa for ALSA, depending on your distribution. |
- You need plugins for Theora, gstreamer0.10-base and MPEG-4 incluing aac (e.g. gst-plugins-faad), gstreamer0.10-bad. For WebM, you'll need plugins for vorbis (-base), matroska (-good), and vp8 (-bad). Have a look at http://www.gstreamer.net/documentation/plugins.html for details. | - You need plugins for Theora, gstreamer(0.10/1.0)-base and MPEG-4 incluing aac (e.g. gst-plugins-faad), gstreamer(0.10/1.0)-bad. For WebM, you'll need plugins for vorbis (-base), matroska (-good), and vp8 (-bad). Have a look at http://www.gstreamer.net/documentation/plugins.html for details. |
- For Youtube or Vimeo, you need WebKitGTK+ 1.1.20 or newer. | - For Youtube or Vimeo, you need WebKitGTK+ 1.1.20 or newer. |
- You can [[http://ie.microsoft.com/testdrive/Graphics/VideoFormatSupport/Default.html|test your installed codecs here]].. | - You can [[http://ie.microsoft.com/testdrive/Graphics/VideoFormatSupport/Default.html|test your installed codecs here]].. |
- Since Midori 0.3.5 you can look at "about:version" to see which video codecs you have installed. | - You can look at about:version to see which video codecs you have installed. |
| |
=== Java doesn't work, applets don't show up === | === Java doesn't work, applets don't show up === |
}</code> | }</code> |
| |
| ====== Midori Architecture ====== |
| |
| Midori stands on the shoulders of three giants in particular: the software libraries [[http://www.gtk.org/|GTK+]], [[http://webkitgtk.org/|WebKitGTK+]], and [[https://developer.gnome.org/libsoup/|libsoup]]. GTK+ provides the buttons, windows and menus, WebKitGTK+ draws and controls web pages, and libsoup downloads those pages. |
| |
===== Understanding WebKit Version Numbers ===== | WebKitGTK+ itself uses two other important libraries: [[https://www.webkit.org/projects/javascript/index.html|JavaScriptCore]], a WebKit project which runs scripts on web pages; and [[http://gstreamer.freedesktop.org/|GStreamer]], which plays HTML5 video and audio. |
| ===== WebKit Version Numbers ===== |
| |
WebKit is the core of the Midori browser and often shows up in bug reports. Because WebKit is a complex piece of software and compatible with various libraries, its version numbers and naming schemes are not always clear to end-users. Read on and be enlightened: | WebKit is the core of the Midori browser, and it determines how web pages are rendered. Because WebKit is a complex piece of software and compatible with various libraries, its version numbers and naming schemes can at times be confusing. |
| |
WebKit itself is a library which works in many environments, such as Windows, OS X, and various Linux DE. There are different "ports", one of which corresponds to each of these environments, and each of which is slightly different in bugs and features at any given time. The WebKit port used by Midori (because Midori is built with GTK+) is WebKitGTK+. | WebKit itself is a library which works in many environments, such as Windows, OS X, and various Linux DE. There are different "ports", one of which corresponds to each of these environments, and each of which is slightly different in bugs and features at any given time. The WebKit port used by Midori (because Midori is built with GTK+) is WebKitGTK+. |
WebKit has a "new API layer ... designed from the ground up to support a split process model"--so pages can crash without the entire browser crashing. This layer is called WebKit2, and for WebKitGTK+ it requires building against GTK+3, producing a library file called libwebkit2gtk-3.0.so. | WebKit has a "new API layer ... designed from the ground up to support a split process model"--so pages can crash without the entire browser crashing. This layer is called WebKit2, and for WebKitGTK+ it requires building against GTK+3, producing a library file called libwebkit2gtk-3.0.so. |
| |
The version of WebKitGTK+ is only interesting from the standpoint of which API features were available and which bugs were present in that particular release; it's best checked by visiting about:version. | To find out the version of WebKitGTK+ your build of Midori is using, visit about:version. |
| |
=== Version Number Interactions === | === Version Number Interactions === |
| |
WebKit2 can be built even with quite old WebKit versions, though Midori's WebKit2 support requires version 2.0.0 or newer of WebKit. Current versions of WebKitGTK+ continues to support GTK+2 and GTK+3 (the latter since 1.4.x or so). As stated above, the WebKit2 API layer is only available with GTK+3. | The WebKit2 API layer is available from fairly old WebKit versions through the present, but Midori's WebKit2 support requires version 2.0.0 or newer of WebKitGTK+. Current versions of WebKitGTK+ continue to support GTK+2 and GTK+3 (the latter since 1.4.x or so). As stated above, the WebKit2 API layer is only available with GTK+3. |
| |
Midori's support for WebKit2 is still provisional, and likely unsuitable for real-world daily usage; much work is being done in this area so that Midori can use WebKit2 by default at some point in the future. | Midori's support for WebKit2 is still provisional, and likely unsuitable for real-world daily usage; much work is being done in this area so that Midori can use WebKit2 by default at some point in the future. |