Xfce Wiki

Sub domains
 

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Last revisionBoth sides next revision
midori:faq [2014/06/04 23:56] – [Midori - Frequently asked questions] gue5tmidori:faq [2017/02/21 14:36] – [Security features] alemao
Line 5: Line 5:
 This is a list of frequently asked questions about the Midori Web Browser. Anyone should feel free to improve or extend this page, but keep it clean and easy to read for other users. This is a list of frequently asked questions about the Midori Web Browser. Anyone should feel free to improve or extend this page, but keep it clean and easy to read for other users.
  
-====== Getting started ======+====== About Midori ======
  
 === What is "Midori" and why should I use it? === === What is "Midori" and why should I use it? ===
-Midori is a Web Browser, that aims to be lightweight and fast. It aligns well with the Xfce philosophy of making the most out of available resources.+Midori is a Web browser that aims to be lightweight and fast. It aligns well with the Xfce philosophy of making the most out of available resources. It has a customizable interface using the GTK+ toolkit.
  
 === How to pronounce Midori and what does the name mean? === === How to pronounce Midori and what does the name mean? ===
Line 17: Line 17:
  
 === On which platforms does Midori run currently? === === On which platforms does Midori run currently? ===
-Midori is basically very portable and should run on all platforms that its dependencies support.+Midori is portable and should run on all platforms that its dependencies support. Releases exist on various Linux distributions, for Windows versions prior to 8.1 (for now), and BSD.
  
 === Under which license is Midori distributed? === === Under which license is Midori distributed? ===
Line 62: Line 62:
 Enable changing hotkeys while hovering menu items: Enable changing hotkeys while hovering menu items:
 <code>gtk-can-change-accels = 1</code> <code>gtk-can-change-accels = 1</code>
 +
 +=== Making the current tab more visible ===
 +
 +To make the current tab more visible in Midori, when running Elementary edit the file /usr/share/themes/elementary/gtk-3.0/gtk-widgets.css around line 1620:
 +
 +<code>.notebook tab .active-page GtkLabel {
 +font-weight: Bold;</code>
 +
 +Note that this will also affect tabs on Files, Scratch and other apps. The change is presumably applicable to other GTK+3 based themes but it wasn't tested.
  
 === Disable middle click pasting === === Disable middle click pasting ===
Line 93: Line 102:
  
 No key store is available or it's incorrectly setup. By default GNOME keyring can do this. Under Xfce it is recommended to enable "GNOME services" under "Session and Startup settings". To make sure, that the output of "gnome-keyring --startup" is correctly sent to the environment, you can add "export `gnome-keyring-daemon --start`" to .xinitrc. No key store is available or it's incorrectly setup. By default GNOME keyring can do this. Under Xfce it is recommended to enable "GNOME services" under "Session and Startup settings". To make sure, that the output of "gnome-keyring --startup" is correctly sent to the environment, you can add "export `gnome-keyring-daemon --start`" to .xinitrc.
 +
 +In order to solve it, follow the steps:\\ 
 +1- make sure that gnome-keyring-pkcs11.so exists in your machine, the location can be found with:\\ 
 +$ sudo find / -name gnome-keyring-pkcs11.so
 +
 +Depending on the architecture it can be under /usr/lib/x86_64-linux-gnu/pkcs11 or /usr/lib/i386-linux-gnu/pkcs11\\ 
 +
 +If you don't find them, you must install it:\\ 
 +
 +**64bit machine: **\\ 
 +$ sudo apt-get install libp11-kit-gnome-keyring
 +
 +**32bit machine: **\\ 
 +$ sudo apt-get install libp11-kit-gnome-keyring:i386
 +
 +After that the file should be in the expected place. 
 +
 +2- Now **CLOSE** Midori.
 +
 +3- After it is totally closed, run:
 +
 +**64bit machine: **\\ 
 +$ modutil -add gnome-keyring -libfile ./lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so  -mechanisms RSA:DSA -dbdir ~/.config/midori/
 +
 +**32bit machine: **\\ 
 +$ modutil -add gnome-keyring -libfile ./lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so  -mechanisms RSA:DSA -dbdir ~/.config/midori/
  
 == A testcase for self-signed certificates == == A testcase for self-signed certificates ==
Line 140: Line 175:
  
 === 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
Line 146: Line 183:
 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:versionto 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 ===
Line 539: Line 576:
 }</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-usersRead on and be enlightened:+WebKit is the core of the Midori browserand 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+.
Line 550: Line 591:
 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 presentbut 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.