Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
midori_faq [2009/09/03 14:36] – Tidying up wording, and added where to find GtkLauncher on a Debian machine. johngh | midori_faq [2010/04/17 13:53] – Moved to midori/faq. kalikiana | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== Midori - Frequently asked questions ====== | ====== Midori - Frequently asked questions ====== | ||
- | This is a list of frequently asked questions about the Midori Web Browser. Anyone feel free to improve and/ or extend this page, but keep it clean and easy to read for other Xfce users. | ||
- | ====== Getting started ====== | ||
- | ===== About Midori ===== | ||
- | === What is " | + | Moved to [[midori/ |
- | 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. | + | |
- | + | ||
- | === How to pronounce Midori and what does the name mean? === | + | |
- | Pronounce it " | + | |
- | + | ||
- | === What does the logo mean? === | + | |
- | The paw of a green cat. Obviously. Also it resembles the letter " | + | |
- | + | ||
- | === On which platforms does Midori run currently? === | + | |
- | Midori is basically very portable and should run on all platforms that its dependencies support. | + | |
- | + | ||
- | === Under which license is Midori distributed? | + | |
- | Midori and all delivered artwork are licensed under the LGPL2. | + | |
- | ===== Common problems ===== | + | |
- | + | ||
- | === There are missing icons/ warnings === | + | |
- | The set of themed icons Midori can use is very limited. For instance icons for a new tab or the throbber are not guaranteed to be available. To fix this, install a Freedesktop.org spec compliant icon theme, such as Tango or Gnome, or one that is compatible with these. | + | |
- | + | ||
- | === Tweaking Midori on the Gtk level === | + | |
- | If you don't have a desktop application that takes care of Gtk settings or if your interface doesn' | + | |
- | + | ||
- | Use Tango as a fallback for your icon theme: | + | |
- | < | + | |
- | gtk-fallback-icon-theme = " | + | |
- | + | ||
- | Use a smaller toolbar: | + | |
- | < | + | |
- | + | ||
- | Enable changing hotkeys while hovering menu items: | + | |
- | < | + | |
- | + | ||
- | === Midori crashes shortly before pages are loaded === | + | |
- | There appears to be an issue with Glib 2.16. The recommended solution is to upgrade your Glib package to 2.18. | + | |
- | + | ||
- | === Flash/ Netscape plugins don't work === | + | |
- | You need to set MOZ_PLUGIN_PATH, | + | |
- | + | ||
- | <code bash> | + | |
- | + | ||
- | You can either run that above line and run Midori in the same terminal afterwards or, for the long term, put it in ~/ | + | |
- | + | ||
- | === HTTPS URLS won't load === | + | |
- | + | ||
- | That's a problem with WebKit. You can work around it to some extent if you start Midori like so: | + | |
- | + | ||
- | <code bash> | + | |
- | + | ||
- | === GIO-2.0 version === | + | |
- | + | ||
- | If you're trying to build midori on an older system, when you run | + | |
- | < | + | |
- | you may get the following message: | + | |
- | + | ||
- | < | + | |
- | Checking for gio-2.0 >= 2.16.0 | + | |
- | Perhaps you should add the directory containing `gio-2.0.pc' | + | |
- | to the PKG_CONFIG_PATH environment variable | + | |
- | No package ' | + | |
- | </ | + | |
- | + | ||
- | This may mean that you don't have libglib2.0-dev installed, or that the version you have is too old. | + | |
- | + | ||
- | On a Debian machine you can check the libglib2.0 version with: | + | |
- | + | ||
- | < | + | |
- | user@debian: | + | |
- | ii libglib2.0-0 | + | |
- | ii libglib2.0-data | + | |
- | ii libglib2.0-dev | + | |
- | </ | + | |
- | + | ||
- | In this case, the libglib2.0 with etch is at 2.12.4-2+etch1, | + | |
- | + | ||
- | + | ||
- | ====== Features ====== | + | |
- | ===== Download Managers ===== | + | |
- | + | ||
- | Midori can start downloads with an external download manager. To use that feature, open up the Preferences and insert the name of a program executable in the Download Manager executable. There is a list of download managers on [[http:// | + | |
- | + | ||
- | === GGet === | + | |
- | + | ||
- | [[http:// | + | |
- | + | ||
- | === wget.sh === | + | |
- | + | ||
- | A simple shell script that uses wget to download the files and informs the user with a notification when the downloads are complete. | + | |
- | + | ||
- | You need a notification daemon, usually you already have the one from GNOME, but there is also [[http:// | + | |
- | + | ||
- | <code bash># | + | |
- | + | ||
- | test -z " | + | |
- | + | ||
- | if [ -f ${XDG_CONFIG_HOME: | + | |
- | . ${XDG_CONFIG_HOME: | + | |
- | fi | + | |
- | XDG_DOWNLOAD_DIR=${XDG_DOWNLOAD_DIR: | + | |
- | + | ||
- | notify-send -t 1500 -u low -i gtk-save Midori\ Download " | + | |
- | $*" | + | |
- | wget " | + | |
- | notify-send -u low -i gtk-save Midori\ Download "The download is complete. | + | |
- | <a href=\" | + | |
- | + | ||
- | ===== Proxy servers ===== | + | |
- | + | ||
- | By running a local proxy you can modify web content even before it has reached Midori. That allows you to do things similar to what user scripts and user styles provide and even others that neither is suitable for. | + | |
- | + | ||
- | To use Midori with a proxy server, there are two options: | + | |
- | + | ||
- | 1. WebKit is built with libcurl. Define an environment variable http_proxy and set it to your proxy server like so: | + | |
- | + | ||
- | export http_proxy = 234.22.154.11: | + | |
- | + | ||
- | 2. WebKit is built with libsoup. Midori >= 0.1.2, is built with libsoup. Try to open some web page. Now open the preferences, | + | |
- | + | ||
- | === Privoxy === | + | |
- | + | ||
- | Privoxy is a non-caching web proxy with filter capabilites and particular support for blocking advertisements before even loading them. | + | |
- | + | ||
- | http:// | + | |
- | + | ||
- | === Mousehole === | + | |
- | + | ||
- | Mousehole is a scriptable proxy server written in Ruby. | + | |
- | + | ||
- | http:// | + | |
- | ===== Mouse Gestures ===== | + | |
- | + | ||
- | Midori has an extension that implements Mouse Gestures now. It is only available in the repository and won't work with a copy older than 2009-01-21. | + | |
- | + | ||
- | For a quick and dirty overview of the gestures in the current release take a look at the [[http:// | + | |
- | Further information is available at the [[http:// | + | |
- | + | ||
- | Additionally, | + | |
- | + | ||
- | ===== Search Engines ===== | + | |
- | + | ||
- | Search engines are tools to ease searches on different web sites. In order to search something with a website, that site must provide a search feature available with a web form. In this example, we will setup a search engine for the English Wikipedia. | + | |
- | + | ||
- | === Step 1: Search the web form, and find the right parameters === | + | |
- | + | ||
- | The search form of the Wikipedia web site is available in the left column. Just enter your search terms (for example " | + | |
- | + | ||
- | === Step 2: Setting up a search engine in Midori === | + | |
- | + | ||
- | Now, open the Search Engine Manager | + | |
- | + | ||
- | + | ||
- | {{http:// | + | |
- | + | ||
- | Here it is | + | |
- | + | ||
- | {{http:// | + | |
- | + | ||
- | If you validate the Add button, you are presented an interface to enter different parameters. Choose a name and a description. Then enter a search URL. That is your previous search URL with your search term replaced with %s. When searching something with that search engine, Midori will use the search URL, replace %s with your search terms, and bring you to computed URL. We don't care about the icon yet. A token can be used as a shorthand for a keyboard search. It's therefore important to use an easy to remember token. For example, we use " | + | |
- | + | ||
- | + | ||
- | {{http:// | + | |
- | + | ||
- | Now, your search engine is created. | + | |
- | + | ||
- | {{http:// | + | |
- | + | ||
- | You can check its presence in the Midori search bar | + | |
- | + | ||
- | {{http:// | + | |
- | + | ||
- | === Step 3: Use your search engine === | + | |
- | + | ||
- | Now, you can use it by typing your search term in the location bar. If you search for " | + | |
- | + | ||
- | + | ||
- | {{http:// | + | |
- | + | ||
- | Tip: You can go through the this tutorial and replace all instances of " | + | |
- | + | ||
- | ===== User scripts ===== | + | |
- | + | ||
- | + | ||
- | === Overview === | + | |
- | + | ||
- | UserScripts are scripts applied on some, or on all web pages. They can modify | + | |
- | + | ||
- | === GreaseMonkey compatibility === | + | |
- | + | ||
- | Midori' | + | |
- | + | ||
- | === How to install a UserScript === | + | |
- | + | ||
- | First, you need to find some scripts (or write your own). You can find some at [[http:// | + | |
- | + | ||
- | To install a userscript, you have to download the script as a file, and put it in the folder **~/ | + | |
- | + | ||
- | Note, if the script is only shown as source code on the page, you first have to create a new text file in a text editor, copy the source code into the new file, and save it as my-user-script.user.js where " | + | |
- | + | ||
- | === Feed (RSS/Atom) reading via a UserScript === | + | |
- | + | ||
- | Midori is indeed sure can handle RSS and ATOM feeds (via it's **Feed Panel** extension) and yet, it's lack of spotting feed addresses makes it pretty difficult to find these addresses on websites that do not have an organized list of feeds addresses. To track those hidden (not well organized) feeds you can use [[http:// | + | |
- | + | ||
- | === Flash blocking via a UserScript === | + | |
- | + | ||
- | You can use [[http:// | + | |
- | + | ||
- | === Flash blocking via a User style === | + | |
- | + | ||
- | You can also use [[http:// | + | |
- | + | ||
- | + | ||
- | ===== User styles ===== | + | |
- | + | ||
- | === Overview === | + | |
- | + | ||
- | User styles are CSS Cascading Style sheets that are loaded locally and applied on top of web pages, similar to User scripts, in order to add or alter functionality and also fix bugs. | + | |
- | + | ||
- | === How to install a user style === | + | |
- | + | ||
- | First, you need to find some styles (or write your own). You can find some at [[http:// | + | |
- | + | ||
- | To install a user style, you have to download the style as a file, and put it in the folder **~/ | + | |
- | + | ||
- | Note, if the style is only shown as source code on the page, you first have to create a new text file in a text editor, copy the source code into the new file, and save it as my-user-style.user.css where " | + | |
- | + | ||
- | === How to install a user style before Midori 0.0.20 === | + | |
- | + | ||
- | Open up the Preferences and use the file chooser button beside User Stylesheet to choose a style sheet file. The style sheet will from now on be applied to all sites automatically. | + | |
- | + | ||
- | === Ad blocking via a User style === | + | |
- | + | ||
- | You can use [[http:// | + | |
- | ===== Reporting a bug ===== | + | |
- | + | ||
- | If you find a bug in Midori, the first step to have it fixed is to report it with Midori' | + | |
- | + | ||
- | === Is the bug related to WebKit or Midori ? === | + | |
- | + | ||
- | Midori is based on the WebKitGtk rendering engine. | + | |
- | + | ||
- | Before opening a bug report in Midori' | + | |
- | If you compiled WebKit yourself, GtkLauncher should be in the **Programs/ | + | |
- | + | ||
- | First, launch GtkLauncher and open the problematic website. If the same problem occurs in | + | |
- | GtkLauncher too, you've probably encountered a bug in WebKit itself. The problem is therefore more likely to be fixed if you report it via the [[http:// | + | |
- | If the problem appears in Midori but not in GtkLauncher, | + |