1043 lines
44 KiB
HTML
1043 lines
44 KiB
HTML
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
|
||
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
||
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en"
|
||
lang="en" dir="ltr">
|
||
<head>
|
||
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
||
<title>midori:faq</title>
|
||
<meta name="generator" content="DokuWiki"/>
|
||
<meta name="robots" content="noindex,nofollow"/>
|
||
<meta name="date" content="2012-09-18T16:25:52+0200"/>
|
||
<meta name="keywords" content="midori,faq"/>
|
||
<link rel="search" type="application/opensearchdescription+xml" href="/lib/exe/opensearch.php" title="Xfce Wiki"/>
|
||
<link rel="start" href="/"/>
|
||
<link rel="contents" href="/midori/faq?do=index" title="Sitemap"/>
|
||
<link rel="alternate" type="application/rss+xml" title="Recent Changes" href="/feed.php"/>
|
||
<link rel="alternate" type="application/rss+xml" title="Current Namespace" href="/feed.php?mode=list&ns=midori"/>
|
||
<link rel="alternate" type="text/html" title="Plain HTML" href="/_export/xhtml/midori/faq"/>
|
||
<link rel="alternate" type="text/plain" title="Wiki Markup" href="/_export/raw/midori/faq"/>
|
||
<link rel="canonical" href="http://wiki.xfce.org/midori/faq"/>
|
||
<link rel="stylesheet" href="faq.css" />
|
||
<link rel="stylesheet" href="faq.css" />
|
||
<link rel="stylesheet" href="faq.css" />
|
||
<script type="text/javascript"><!--//--><![CDATA[//><!--
|
||
var NS='midori';var JSINFO = {"id":"midori:faq","namespace":"midori"};
|
||
//--><!]]></script>
|
||
<script type="text/javascript" charset="utf-8" src="/lib/exe/js.php?tseed=1334991875"></script>
|
||
</head>
|
||
<body>
|
||
<div class="dokuwiki export">
|
||
<!-- TOC START -->
|
||
<div class="toc">
|
||
<div class="tocheader toctoggle" id="toc__header">Table of Contents</div>
|
||
<div id="toc__inside">
|
||
|
||
<ul class="toc">
|
||
<li class="level1"><div class="li"><span class="li"><a href="#midori_-_frequently_asked_questions" class="toc">Midori - Frequently asked questions</a></span></div></li>
|
||
<li class="level1"><div class="li"><span class="li"><a href="#getting_started" class="toc">Getting started</a></span></div></li>
|
||
<li class="level1"><div class="li"><span class="li"><a href="#common_problems" class="toc">Common problems</a></span></div>
|
||
<ul class="toc">
|
||
<li class="level2"><div class="li"><span class="li"><a href="#security_features" class="toc">Security features</a></span></div></li>
|
||
<li class="level2"><div class="li"><span class="li"><a href="#flash_doesn_t_work" class="toc">Flash doesn't work</a></span></div></li>
|
||
</ul>
|
||
</li>
|
||
<li class="level1"><div class="li"><span class="li"><a href="#privacy" class="toc">Privacy</a></span></div>
|
||
<ul class="toc">
|
||
<li class="level2"><div class="li"><span class="li"><a href="#blacklist_cookies" class="toc">Blacklist cookies</a></span></div></li>
|
||
<li class="level2"><div class="li"><span class="li"><a href="#adblock" class="toc">Adblock</a></span></div></li>
|
||
</ul>
|
||
</li>
|
||
<li class="level1"><div class="li"><span class="li"><a href="#modes" class="toc">Modes</a></span></div>
|
||
<ul class="toc">
|
||
<li class="level2"><div class="li"><span class="li"><a href="#web_applications" class="toc">Web Applications</a></span></div></li>
|
||
<li class="level2"><div class="li"><span class="li"><a href="#private_browsing" class="toc">Private Browsing</a></span></div></li>
|
||
<li class="level2"><div class="li"><span class="li"><a href="#portable_modewin32" class="toc">Portable mode/ Win32</a></span></div></li>
|
||
<li class="level2"><div class="li"><span class="li"><a href="#kiosk_mode" class="toc">Kiosk mode</a></span></div></li>
|
||
</ul>
|
||
</li>
|
||
<li class="level1"><div class="li"><span class="li"><a href="#proxy_servers" class="toc">Proxy servers</a></span></div></li>
|
||
<li class="level1"><div class="li"><span class="li"><a href="#keyboard_hotkeys" class="toc">Keyboard Hotkeys</a></span></div></li>
|
||
<li class="level1"><div class="li"><span class="li"><a href="#mouse_gestures" class="toc">Mouse Gestures</a></span></div></li>
|
||
<li class="level1"><div class="li"><span class="li"><a href="#user_scripts_and_styles" class="toc">User scripts and styles</a></span></div>
|
||
<ul class="toc">
|
||
<li class="level2"><div class="li"><span class="li"><a href="#user_styles" class="toc">User styles</a></span></div></li>
|
||
</ul></li>
|
||
</ul>
|
||
</div>
|
||
</div>
|
||
<!-- TOC END -->
|
||
|
||
<h1 class="sectionedit1"><a name="midori_-_frequently_asked_questions" id="midori_-_frequently_asked_questions">Midori - Frequently asked questions</a></h1>
|
||
<div class="level1">
|
||
|
||
<p>
|
||
<strong>This document is licensed under the <acronym title="GNU Lesser General Public License">LGPL</acronym> 2.1.</strong>
|
||
</p>
|
||
|
||
<p>
|
||
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.
|
||
</p>
|
||
<p>
|
||
This is a snapshot of Frequently Asked Questions designated for offline viewing. The most recent version of this document can be found <a href="http://wiki.xfce.org/midori/faq">in the Xfce wiki</a>.
|
||
<p/>
|
||
|
||
</div>
|
||
|
||
<h1 class="sectionedit2"><a name="getting_started" id="getting_started">Getting started</a></h1>
|
||
<div class="level1">
|
||
|
||
</div>
|
||
|
||
<h4><a name="what_is_midori_and_why_should_i_use_it" id="what_is_midori_and_why_should_i_use_it">What is "Midori" and why should I use it?</a></h4>
|
||
<div class="level4">
|
||
|
||
<p>
|
||
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.
|
||
</p>
|
||
|
||
</div>
|
||
|
||
<h4><a name="how_to_pronounce_midori_and_what_does_the_name_mean" id="how_to_pronounce_midori_and_what_does_the_name_mean">How to pronounce Midori and what does the name mean?</a></h4>
|
||
<div class="level4">
|
||
|
||
<p>
|
||
Pronounce it “midoɺi”, with a Spanish/ Japanese “r” or “Mee-Doh-Ree” in English or read it Italian. The name comes from the Japanese word 緑 (みどり) for the colour “green”.
|
||
</p>
|
||
|
||
</div>
|
||
|
||
<h4><a name="what_does_the_logo_mean" id="what_does_the_logo_mean">What does the logo mean?</a></h4>
|
||
<div class="level4">
|
||
|
||
<p>
|
||
The paw of a green cat. Obviously. Also it resembles the letter “M” in “Midori”. The curving is supposed to emphasize speed.
|
||
</p>
|
||
|
||
</div>
|
||
|
||
<h4><a name="on_which_platforms_does_midori_run_currently" id="on_which_platforms_does_midori_run_currently">On which platforms does Midori run currently?</a></h4>
|
||
<div class="level4">
|
||
|
||
<p>
|
||
Midori is basically very portable and should run on all platforms that its dependencies support.
|
||
</p>
|
||
|
||
</div>
|
||
|
||
<h4><a name="under_which_license_is_midori_distributed" id="under_which_license_is_midori_distributed">Under which license is Midori distributed?</a></h4>
|
||
<div class="level4">
|
||
|
||
<p>
|
||
Midori and all delivered artwork are licensed under the LGPL2.
|
||
</p>
|
||
|
||
</div>
|
||
|
||
<h1 class="sectionedit3"><a name="common_problems" id="common_problems">Common problems</a></h1>
|
||
<div class="level1">
|
||
|
||
</div>
|
||
|
||
<h4><a name="why_does_google_mailcalendarmaps_facebook_not_work_or_show_mobile_version" id="why_does_google_mailcalendarmaps_facebook_not_work_or_show_mobile_version">Why does Google Mail/ Calendar/ Maps, Facebook not work or show mobile version?</a></h4>
|
||
<div class="level4">
|
||
|
||
<p>
|
||
Some websites discriminate against your browser.
|
||
</p>
|
||
|
||
<p>
|
||
If you have Midori older than 0.3.5, go to Preferences > Network > Identify As, and choose Custom. Paste this into the entry:
|
||
</p>
|
||
|
||
<p>
|
||
Mozilla/5.0 (X11; Linux) AppleWebKit/531.2+ Midori/0.3
|
||
</p>
|
||
|
||
<p>
|
||
If this doesn't do the trick, try choosing Safari or Firefox.
|
||
</p>
|
||
|
||
<p>
|
||
Many other websites use similar means of detecting the browser.
|
||
</p>
|
||
|
||
<p>
|
||
Ideally Google would follow <a href="http://code.google.com/p/doctype/wiki/ArticleGoogleChromeCompatFAQ#UserAgent_Detection" class="urlextern" title="http://code.google.com/p/doctype/wiki/ArticleGoogleChromeCompatFAQ#UserAgent_Detection" rel="nofollow">their own recommendation</a> at some point.
|
||
</p>
|
||
|
||
</div>
|
||
|
||
<h4><a name="there_are_missing_iconswarnings" id="there_are_missing_iconswarnings">There are missing icons/ warnings</a></h4>
|
||
<div class="level4">
|
||
|
||
<p>
|
||
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 <acronym title="specification">spec</acronym> compliant icon theme, such as Elementary, Faenza, Buuf or GNOME.
|
||
</p>
|
||
|
||
</div>
|
||
|
||
<h4><a name="tweaking_midori_on_the_gtk_level" id="tweaking_midori_on_the_gtk_level">Tweaking Midori on the Gtk level</a></h4>
|
||
<div class="level4">
|
||
|
||
<p>
|
||
If you don't have a desktop application that takes care of Gtk settings or if your interface doesn't support a particular feature, you can modify any settings easily manually by specifying them in a text file called ~/.gtkrc-2.0 or /etc/gtk-2.0/gtkrc:
|
||
</p>
|
||
|
||
<p>
|
||
Use Tango as a fallback for your icon theme:
|
||
</p>
|
||
<pre class="code">gtk-icon-theme-name = "MySuperFancyTheme"
|
||
gtk-fallback-icon-theme = "Tango"</pre>
|
||
|
||
<p>
|
||
Use a smaller toolbar:
|
||
</p>
|
||
<pre class="code">gtk-toolbar-icon-size = GTK_ICON_SIZE_SMALL_TOOLBAR</pre>
|
||
|
||
<p>
|
||
Only for those not running a complete DE like Xfce, Elementary, etc…<br/>
|
||
|
||
There is a preference: Preferences → Browsing → Toolbar Style: Small icons
|
||
</p>
|
||
|
||
<p>
|
||
Enable changing hotkeys while hovering menu items:
|
||
</p>
|
||
<pre class="code">gtk-can-change-accels = 1</pre>
|
||
|
||
</div>
|
||
|
||
<h4><a name="midori_crashes_shortly_before_pages_are_loaded" id="midori_crashes_shortly_before_pages_are_loaded">Midori crashes shortly before pages are loaded</a></h4>
|
||
<div class="level4">
|
||
|
||
<p>
|
||
There appears to be an issue with Glib 2.16. The recommended solution is to upgrade your Glib package to 2.18.
|
||
</p>
|
||
|
||
</div>
|
||
|
||
<h4><a name="how_can_i_change_the_cache_folder_to_tmpfs" id="how_can_i_change_the_cache_folder_to_tmpfs">How can I change the cache folder (to tmpfs)?</a></h4>
|
||
<div class="level4">
|
||
|
||
<p>
|
||
On Linux and BSD, you can set XDG_CACHE_HOME for all applications, or just Midori. Midori saves icons and cache files in that location. The default is ~/.cache.
|
||
</p>
|
||
|
||
<p>
|
||
export XDG_CACHE_HOME=/dev/shm
|
||
</p>
|
||
|
||
</div>
|
||
|
||
<h2 class="sectionedit4"><a name="security_features" id="security_features">Security features</a></h2>
|
||
<div class="level2">
|
||
|
||
</div>
|
||
|
||
<h4><a name="hstshttp_strict_transport_security" id="hstshttp_strict_transport_security">HSTS/ HTTP Strict Transport Security</a></h4>
|
||
<div class="level4">
|
||
|
||
<p>
|
||
Midori >= 0.4.7 automatically picks up the Strict-Transport-Security header and caches sites locally. By design, there's no UI. System administrators can however place a pre-loaded cache at /etc/xdg/midori/hsts.
|
||
</p>
|
||
|
||
</div>
|
||
|
||
<h4><a name="certificate_handling" id="certificate_handling">Certificate Handling</a></h4>
|
||
<div class="level4">
|
||
|
||
<p>
|
||
Midori >= 0.4.7 supports <a href="/midori/gcr" class="wikilink2" title="midori:gcr" rel="nofollow">http://git.gnome.org/browse/gcr/tree/gcr</a> for certificate display and management, you can click the lock in the urlbar to see detailed information. Earlier versions, or one without gcr will not handle certificates beyond the lock icon in the urlbar.
|
||
</p>
|
||
|
||
</div>
|
||
|
||
<h5><a name="error_granting_trustcouldn_t_find_a_place_to_store_the_imported_certificate" id="error_granting_trustcouldn_t_find_a_place_to_store_the_imported_certificate">Error granting trust: Couldn't find a place to store the imported certificate</a></h5>
|
||
<div class="level5">
|
||
|
||
<p>
|
||
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”. Otherwise this can occur if a script doesn't correctly send the output of “gnome-keyring –startup” to the environment.
|
||
</p>
|
||
|
||
</div>
|
||
|
||
<h5><a name="a_testcase_for_self-signed_certificates" id="a_testcase_for_self-signed_certificates">A testcase for self-signed certificates</a></h5>
|
||
<div class="level5">
|
||
|
||
<p>
|
||
<a href="https://selfsigned.notyours.dk:444/menu.gif" class="urlextern" title="https://selfsigned.notyours.dk:444/menu.gif" rel="nofollow">https://selfsigned.notyours.dk:444/menu.gif</a>
|
||
</p>
|
||
|
||
</div>
|
||
|
||
<h2 class="sectionedit5"><a name="flash_doesn_t_work" id="flash_doesn_t_work">Flash doesn't work</a></h2>
|
||
<div class="level2">
|
||
|
||
</div>
|
||
|
||
<h4><a name="windows_support" id="windows_support">Windows support</a></h4>
|
||
<div class="level4">
|
||
|
||
<p>
|
||
WebKitGTK+ and thusly Midori on Windows doesn't support Flash or any other plugins. If WebKitGTK+ adds the feature in the future, we will support it. For now there's nothing we can do.
|
||
</p>
|
||
|
||
<p>
|
||
Starting with WebkitGTK+ 1.8.2 (Midori 0.4.7) Netscape plugins are now supported.
|
||
Midori should pick them up from standard netscape plugins locations.
|
||
</p>
|
||
|
||
</div>
|
||
|
||
<h4><a name="netscape_plugins_on_linux_bsd_and_os_x" id="netscape_plugins_on_linux_bsd_and_os_x">Netscape plugins on Linux, BSD and OS X</a></h4>
|
||
<div class="level4">
|
||
|
||
<p>
|
||
You need to set MOZ_PLUGIN_PATH, for example like this:
|
||
</p>
|
||
<pre class="code bash"><span class="kw3">export</span> <span class="re2">MOZ_PLUGIN_PATH</span>=<span class="st0">"/usr/lib/mozilla/plugins"</span></pre>
|
||
|
||
<p>
|
||
The official Flash plugin is called libflashplayer.so .
|
||
</p>
|
||
|
||
<p>
|
||
You can either run that above line and run Midori in the same terminal afterwards or, for the long term, put it in ~/.bash_profile or /etc/profile.d or your respective distribution's place for this.
|
||
</p>
|
||
|
||
</div>
|
||
|
||
<h4><a name="flash_is_crashingno_flash_with_gtk_3" id="flash_is_crashingno_flash_with_gtk_3">Flash is crashing/ No Flash with GTK+3</a></h4>
|
||
<div class="level4">
|
||
|
||
<p>
|
||
nspluginwrapper is a program that runs Flash and other Netscape plugins in a separate process. So a crash can't cresh the whole browser and Flash, which is GTK+2 can run in GTK+3.
|
||
</p>
|
||
|
||
<p>
|
||
sudo apt-get install nspluginwrapper
|
||
sudo nspluginwrapper -i /usr/lib/flashplugin-installer/libflashplayer.so
|
||
nspluginwrapper -v -a -n -i
|
||
</p>
|
||
|
||
</div>
|
||
|
||
<h4><a name="https_urls_won_t_load" id="https_urls_won_t_load">HTTPS URLS won't load</a></h4>
|
||
<div class="level4">
|
||
|
||
<p>
|
||
That's a problem with WebKit. You can work around it to some extent if you start Midori like so:
|
||
</p>
|
||
<pre class="code bash"><span class="kw3">export</span> <span class="re2">WEBKIT_IGNORE_SSL_ERRORS</span>=<span class="st0">"1"</span> midori</pre>
|
||
|
||
</div>
|
||
|
||
<h4><a name="bit_encryption_isn_t_supported" id="bit_encryption_isn_t_supported">256-bit encryption isn't supported?</a></h4>
|
||
<div class="level4">
|
||
|
||
<p>
|
||
There's no official support right now. It's possible to <a href="https://opensource.conformal.com/fluxbb/viewtopic.php?pid=1332#p1332" class="urlextern" title="https://opensource.conformal.com/fluxbb/viewtopic.php?pid=1332#p1332" rel="nofollow">patch glib-networking to enable 256-bit SSL</a>.
|
||
</p>
|
||
|
||
</div>
|
||
|
||
<h4><a name="scroll_with_middle_mouse_buttonpan-scrolling" id="scroll_with_middle_mouse_buttonpan-scrolling">Scroll with middle mouse button/ pan-scrolling</a></h4>
|
||
<div class="level4">
|
||
|
||
<p>
|
||
<a href="http://ubuntuforums.org/showthread.php?t=478418" class="urlextern" title="http://ubuntuforums.org/showthread.php?t=478418" rel="nofollow">http://ubuntuforums.org/showthread.php?t=478418</a>
|
||
</p>
|
||
|
||
<p>
|
||
Bug: <a href="https://bugs.launchpad.net/webkit/+bug/871425" class="urlextern" title="https://bugs.launchpad.net/webkit/+bug/871425" rel="nofollow">https://bugs.launchpad.net/webkit/+bug/871425</a><br/>
|
||
|
||
Upstream Bug: <a href="https://bugs.webkit.org/show_bug.cgi?id=50561" class="urlextern" title="https://bugs.webkit.org/show_bug.cgi?id=50561" rel="nofollow">https://bugs.webkit.org/show_bug.cgi?id=50561</a>
|
||
</p>
|
||
|
||
</div>
|
||
|
||
<h4><a name="html5_video_doesn_t_play" id="html5_video_doesn_t_play">HTML5 Video doesn't play</a></h4>
|
||
<div class="level4">
|
||
|
||
<p>
|
||
You need to have GStreamer plugins installed which implement the codecs.
|
||
</p>
|
||
<ol>
|
||
<li class="level1"><div class="li"> You need gstreamer0.10-pulse if you're using PulseAudio.</div>
|
||
</li>
|
||
<li class="level1"><div class="li"> You may need gstreamer0.10-alsa for ALSA, depending on your distribution.</div>
|
||
</li>
|
||
<li class="level1"><div class="li"> You need plugins for Theora, gstreamer0.10-base and <acronym title="Moving Picture Experts Group">MPEG</acronym>-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 <a href="http://www.gstreamer.net/documentation/plugins.html" class="urlextern" title="http://www.gstreamer.net/documentation/plugins.html" rel="nofollow">http://www.gstreamer.net/documentation/plugins.html</a> for details.</div>
|
||
</li>
|
||
<li class="level1"><div class="li"> For Youtube or Vimeo, you need WebKitGTK+ 1.1.20 or newer.</div>
|
||
</li>
|
||
<li class="level1"><div class="li"> You can <a href="http://ie.microsoft.com/testdrive/Graphics/VideoFormatSupport/Default.html" class="urlextern" title="http://ie.microsoft.com/testdrive/Graphics/VideoFormatSupport/Default.html" rel="nofollow">test your installed codecs here</a>..</div>
|
||
</li>
|
||
<li class="level1"><div class="li"> Since Midori 0.3.5 you can look at “about:version” to see which video codecs you have installed.</div>
|
||
</li>
|
||
</ol>
|
||
|
||
</div>
|
||
|
||
<h4><a name="java_doesn_t_work_applets_don_t_show_up" id="java_doesn_t_work_applets_don_t_show_up">Java doesn't work, applets don't show up</a></h4>
|
||
<div class="level4">
|
||
|
||
<p>
|
||
Java is supported in WebKitGTK+ since 1.1.22. If you need Java, you need to upgrade to at least that version. Sun/ Oracle Java as well as IcedTea are known to work. Distribution specific setup might be required, such as setting LD_LIBRARY_PATH to include the location of libxul.so and making a symbolic link for libnpjp2.so to /usr/lib/mozilla.
|
||
</p>
|
||
|
||
<p>
|
||
icedtea6 version 1.8 and above has been known to crash midori. If this is the case for you, try sun-jre.
|
||
</p>
|
||
|
||
</div>
|
||
|
||
<h4><a name="how_do_i_get_rid_of_the_menubar" id="how_do_i_get_rid_of_the_menubar">How do I get rid of the menubar?</a></h4>
|
||
<div class="level4">
|
||
|
||
<p>
|
||
In the menubar, go to View → Toolbars → Menubar, voilà the menubar is gone and a new icon appears at the right end of the toolbar. Click the icon to access functionality that otherwise sits in the menubar.
|
||
Midori 0.3.2 disables the menubar by default.
|
||
</p>
|
||
|
||
</div>
|
||
|
||
<h4><a name="why_can_t_i_use_periods_when_searching_from_the_location_bar" id="why_can_t_i_use_periods_when_searching_from_the_location_bar">Why can't I use periods when searching from the location bar?</a></h4>
|
||
<div class="level4">
|
||
|
||
<p>
|
||
Midori tries to make a smart guess on whether you are searching for something or typing a valid address by hand. Yet there are ambiguous cases so it fails.
|
||
</p>
|
||
|
||
<p>
|
||
Try using 'g' in front of the search terms, like 'g Ms.Marple'. The 'g' is a token that tells the browser you want to use Google. See Tools > Manage Search Engines or right-click the location bar and select the menu item, to look at search engines and tokens.
|
||
</p>
|
||
|
||
</div>
|
||
|
||
<h4><a name="how_can_i_reload_and_bypass_the_cache" id="how_can_i_reload_and_bypass_the_cache">How can I reload and bypass the cache?</a></h4>
|
||
<div class="level4">
|
||
|
||
<p>
|
||
Hold the Shift key while clicking Refresh in the toolbar (this works in Chromium, Mozilla, Opera and Safari, too).
|
||
Since Midori 0.3.2 you can use Ctrl+Shift+R.
|
||
</p>
|
||
|
||
</div>
|
||
|
||
<h4><a name="how_do_i_make_tabs_pinnedstickyminimized" id="how_do_i_make_tabs_pinnedstickyminimized">How do I make tabs pinned/ sticky/ minimized?</a></h4>
|
||
<div class="level4">
|
||
|
||
<p>
|
||
Right-click the tab label, and click 'Minimize' or 'Show Tab Icon Only' (Midori 0.3.5 or older).
|
||
</p>
|
||
|
||
</div>
|
||
|
||
<h4><a name="why_doesn_t_google_live_search_work" id="why_doesn_t_google_live_search_work">Why doesn't Google "live search" work?</a></h4>
|
||
<div class="level4">
|
||
|
||
<p>
|
||
You need to set Preferences > Network > Identify As to Firefox.
|
||
</p>
|
||
|
||
</div>
|
||
|
||
<h4><a name="opening_html_email_with_mutt" id="opening_html_email_with_mutt">Opening html email with Mutt</a></h4>
|
||
<div class="level4">
|
||
|
||
<p>
|
||
Place the following in ~/.mutt/mailcap or ~/.mailcap:
|
||
</p>
|
||
<pre class="code">text/html; midori -a '%s'; test=test -n "$DISPLAY"; nametemplate=%s.html</pre>
|
||
|
||
</div>
|
||
|
||
<h4><a name="scrolling_on_website_xyz_is_very_slow" id="scrolling_on_website_xyz_is_very_slow">Scrolling on website xyz is very slow</a></h4>
|
||
<div class="level4">
|
||
<ol>
|
||
<li class="level1"><div class="li"> Go to Tools > Extensions</div>
|
||
</li>
|
||
<li class="level1"><div class="li"> Enable 'User Addons' if it's not yet enabled</div>
|
||
</li>
|
||
<li class="level1"><div class="li"> Create a text file .local/share/midori/styles/scrollfix.user.css</div>
|
||
</li>
|
||
<li class="level1"><div class="li"> Put this into the file: * {-webkit-box-shadow: none !important;}</div>
|
||
</li>
|
||
</ol>
|
||
|
||
</div>
|
||
|
||
<h4><a name="file_opening_doesn_t_workpdfs_are_opened_with_gimp" id="file_opening_doesn_t_workpdfs_are_opened_with_gimp">File opening doesn't work/ PDFs are opened with GIMP</a></h4>
|
||
<div class="level4">
|
||
|
||
<p>
|
||
Midori opens files with GIO, and falls back to xdg-open, exo-open or gnome-open if these are available. All of this relies on freedesktop.org <acronym title="Multipurpose Internet Mail Extension">MIME</acronym> configuration. To tweak this there are multiple options:
|
||
</p>
|
||
<ol>
|
||
<li class="level1"><div class="li"> Use 'Open With' with a graphical file manager</div>
|
||
</li>
|
||
<li class="level1"><div class="li"> Edit ~/.local/share/applications/defaults.list with a text editor</div>
|
||
</li>
|
||
<li class="level1"><div class="li"> Run something like ‘xdg-mime default evince.desktop application/pdf’</div>
|
||
</li>
|
||
</ol>
|
||
|
||
<p>
|
||
xdg-open knows how to handle GNOME, KDE and Xfce.
|
||
LXDE is unfortunately not supported yet, see <a href="https://bugs.freedesktop.org/show_bug.cgi?id=26058" class="urlextern" title="https://bugs.freedesktop.org/show_bug.cgi?id=26058" rel="nofollow">https://bugs.freedesktop.org/show_bug.cgi?id=26058</a>
|
||
</p>
|
||
|
||
</div>
|
||
|
||
<h4><a name="open_magnetircaptand_friends_with_an_application" id="open_magnetircaptand_friends_with_an_application">Open magnet:, irc:, apt: and friends with an application</a></h4>
|
||
<div class="level4">
|
||
|
||
<p>
|
||
As of git 2011-03-05 02:40:00 UTC and Midori 0.3.3 you can
|
||
</p>
|
||
|
||
<p>
|
||
Add a line to ~/.local/share/applications/mimeapps.list:
|
||
</p>
|
||
<pre class="code">x-scheme-handler/magnet=transmission-gtk.desktop</pre>
|
||
|
||
<p>
|
||
Or install an application which advertises the scheme like so:
|
||
</p>
|
||
<pre class="code">MimeType=x-scheme-handler/magnet;</pre>
|
||
|
||
<p>
|
||
Note that incomplete .desktop files will silently fail and it will look as if it doesn't exist.
|
||
</p>
|
||
|
||
</div>
|
||
|
||
<h4><a name="spell_check" id="spell_check">Spell check</a></h4>
|
||
<div class="level4">
|
||
|
||
<p>
|
||
First enable spell checking:
|
||
Edit→Preferences→Behavior and check “Enable Spell Checking”.
|
||
</p>
|
||
|
||
<p>
|
||
Now while typing any errors should get underlined in red. To get suggestions, highlight the word and right-click. You should see a list of suggestions at the top of the menu.
|
||
</p>
|
||
|
||
<p>
|
||
On Windows <a href="http://download.services.openoffice.org/files/contrib/dictionaries/" class="urlextern" title="http://download.services.openoffice.org/files/contrib/dictionaries/" rel="nofollow">you need to download OpenOffice dictionaries</a>, find the zipped file(s) for your locale(s) and unpack the contents into share/myspell/dicts/ in your Midori installation. The folder should contain *.aff and *.dic files
|
||
</p>
|
||
|
||
</div>
|
||
|
||
<h4><a name="is_it_possible_to_disable_same_origin_policy_what_webkit_settings_not_in_the_preferences_can_i_change" id="is_it_possible_to_disable_same_origin_policy_what_webkit_settings_not_in_the_preferences_can_i_change">Is it possible to disable Same Origin Policy? What Webkit settings not in the preferences can I change?</a></h4>
|
||
<div class="level4">
|
||
|
||
<p>
|
||
You can change <a href="http://webkitgtk.org/reference/webkitgtk/stable/WebKitWebSettings.html" class="urlextern" title="http://webkitgtk.org/reference/webkitgtk/stable/WebKitWebSettings.html" rel="nofollow">all values of WebKitWebSettings</a> in the config file (~/.config/midori/config on unices, %APPDATA%\midori\config [please check :)] on Windows). For example, to disable Same Origin Policy for local files, add
|
||
</p>
|
||
<pre class="code">enable-universal-access-from-file-uris=true</pre>
|
||
|
||
<p>
|
||
to your config file.
|
||
</p>
|
||
|
||
</div>
|
||
|
||
<h4><a name="how_do_i_change_the_proxy_server_from_the_toolbar_or_statusbar" id="how_do_i_change_the_proxy_server_from_the_toolbar_or_statusbar">How do I change the proxy server from the toolbar or statusbar?</a></h4>
|
||
<div class="level4">
|
||
<ol>
|
||
<li class="level1"><div class="li"> Activate the Statusbar Features plugin.</div>
|
||
</li>
|
||
<li class="level1"><div class="li"> Close Midori.</div>
|
||
</li>
|
||
<li class="level1"><div class="li"> Create a folder ~/.config/midori/extensions/libstatusbar-features.so/</div>
|
||
</li>
|
||
<li class="level1"><div class="li"> Create a text file “config”</div>
|
||
</li>
|
||
<li class="level1"><div class="li"> Type the following for the default setup:</div>
|
||
</li>
|
||
</ol>
|
||
<pre class="code"> [settings]
|
||
items=auto-load-images;enable-scripts;enable-plugins;identify-as;zoom-level</pre>
|
||
|
||
<p>
|
||
Add button types separated by semicolon:
|
||
</p>
|
||
<ul>
|
||
<li class="level1"><div class="li"> proxy-type Proxy Server</div>
|
||
</li>
|
||
<li class="level1"><div class="li"> preferred-encoding Character Set/ Encoding</div>
|
||
</li>
|
||
<li class="level1"><div class="li"> enable-spell-checking Spell Check</div>
|
||
</li>
|
||
<li class="level1"><div class="li"> zoom-text-and-images Only zoom in text, or text and images</div>
|
||
</li>
|
||
<li class="level1"><div class="li"> first-party-cookies-only First party cookies only</div>
|
||
</li>
|
||
<li class="level1"><div class="li"> site-data-rules see <a href="#blacklist_cookies" title="midori:faq ↵" class="wikilink1">Blacklisting cookies</a></div>
|
||
</li>
|
||
</ul>
|
||
|
||
<p>
|
||
Most settings listed at <a href="http://webkitgtk.org/reference/webkitgtk/stable/WebKitWebSettings.html" class="urlextern" title="http://webkitgtk.org/reference/webkitgtk/stable/WebKitWebSettings.html" rel="nofollow">http://webkitgtk.org/reference/webkitgtk/stable/WebKitWebSettings.html</a> will also work as button types.
|
||
</p>
|
||
|
||
</div>
|
||
|
||
<h1 class="sectionedit6"><a name="privacy" id="privacy">Privacy</a></h1>
|
||
<div class="level1">
|
||
|
||
</div>
|
||
|
||
<h2 class="sectionedit7"><a name="blacklist_cookies" id="blacklist_cookies">Blacklist cookies</a></h2>
|
||
<div class="level2">
|
||
|
||
<p>
|
||
As of Midori 0.4.4 you can add a hidden option to ~/.config/midori/config like so:
|
||
</p>
|
||
<pre class="code">site-data-rules=-google.com,-facebook.com,!bugzilla.gnome.org,+bugs.launchpad.net</pre>
|
||
<ol>
|
||
<li class="level1"><div class="li"> Values prefixed with ”-” are always blocked</div>
|
||
</li>
|
||
<li class="level1"><div class="li"> Values prefixed with ”+” are always accepted</div>
|
||
</li>
|
||
<li class="level1"><div class="li"> Values prefixed with ”!” are not cleared in Clear Private Data</div>
|
||
</li>
|
||
<li class="level1"><div class="li"> No wildcards.</div>
|
||
</li>
|
||
<li class="level1"><div class="li"> LSO, local storage and application caches ignore all policies.</div>
|
||
</li>
|
||
</ol>
|
||
|
||
<p>
|
||
The feature is currently experimental and will change in future versions.
|
||
</p>
|
||
|
||
</div>
|
||
|
||
<h2 class="sectionedit8"><a name="adblock" id="adblock">Adblock</a></h2>
|
||
<div class="level2">
|
||
|
||
<p>
|
||
The Advertisement Blocker can be activated under Extensions. It uses the same lists as Adblock Plus. URLs are blocked completely and never loaded. Lists can be added through the option button on the right side in the extension list.
|
||
</p>
|
||
|
||
</div>
|
||
|
||
<h1 class="sectionedit9"><a name="modes" id="modes">Modes</a></h1>
|
||
<div class="level1">
|
||
|
||
</div>
|
||
|
||
<h2 class="sectionedit10"><a name="web_applications" id="web_applications">Web Applications</a></h2>
|
||
<div class="level2">
|
||
|
||
<p>
|
||
There are two closely related features to open websites as dedicated windows of their own. You can do the following to use them:
|
||
</p>
|
||
<ol>
|
||
<li class="level1"><div class="li"> Right-click a hyperlink → Open as Web Application</div>
|
||
</li>
|
||
<li class="level1"><div class="li"> Add or Edit a bookmark → [x] Run as web application</div>
|
||
</li>
|
||
<li class="level1"><div class="li"> Type ‘midori -a <a href="http://foo.bar" class="urlextern" title="http://foo.bar" rel="nofollow">http://foo.bar</a>’ on a command line</div>
|
||
</li>
|
||
</ol>
|
||
|
||
<p>
|
||
You can also add options such as ‘-e Fullscreen’, ‘-e Navigationbar’ or ‘-e Statusbar’ (as of Midori 0.2.9 ‘midori –help-execute will list all available commands’)
|
||
</p>
|
||
|
||
</div>
|
||
|
||
<h2 class="sectionedit11"><a name="private_browsing" id="private_browsing">Private Browsing</a></h2>
|
||
<div class="level2">
|
||
|
||
<p>
|
||
File menu/ App Menu button → Private Browsing
|
||
</p>
|
||
|
||
<p>
|
||
A private window is a separate process, so crashes don't affect the normal browser session. No sensitive data such as cookies, history or bookmarks are stored. No extensions are loaded. Panels are not available.
|
||
</p>
|
||
|
||
<p>
|
||
As of Midori 0.2.9 Private Browsing uses preferences, cookies, keyboard shortcuts and search engines from the normal session, but it won't save any changes. This behaviour can be emulated from the command line with ”-a” and ”-c”.
|
||
</p>
|
||
|
||
<p>
|
||
As of Midori 0.3.4 the –private command line switch opens a private browsing instance with normal preferences, cookies, shortcuts and search engines. But no changes will be saved.
|
||
<acronym title="Domain Name System">DNS</acronym> prefetching is disabled in this mode, also referrers are stripped down to the hostname when navigating between different websites.
|
||
</p>
|
||
|
||
<p>
|
||
The same options available to -a/ –app can be used for private browsing mode.
|
||
</p>
|
||
|
||
</div>
|
||
|
||
<h2 class="sectionedit12"><a name="portable_modewin32" id="portable_modewin32">Portable mode/ Win32</a></h2>
|
||
<div class="level2">
|
||
|
||
<p>
|
||
On Windows builds, -P/ –portable causes all data to be written to the “profile” folder in the Midori folder. Everything, including temporary files and cache, is stored in a sub-folder without touching the system. So Midori can be run eg. from a USB stick on different machines.
|
||
</p>
|
||
|
||
</div>
|
||
|
||
<h2 class="sectionedit13"><a name="kiosk_mode" id="kiosk_mode">Kiosk mode</a></h2>
|
||
<div class="level2">
|
||
|
||
<p>
|
||
There is no specific mode, instead you use several command line switches. A typical fullscreen setup with no toolbar that opens about:blank and resets the session after 2 minutes of inactivity for instance:
|
||
</p>
|
||
<pre class="code bash">midori <span class="re5">-i</span> <span class="nu0">120</span> <span class="re5">-e</span> Fullscreen <span class="re5">-e</span> Navigationbar <span class="re5">-a</span> about:blank</pre>
|
||
|
||
<p>
|
||
Available commands for -e can be listed with “midori –help-execute”.
|
||
</p>
|
||
|
||
<p>
|
||
If needed, a customized profile can be created with “midori -c /path/to/folder”. Using the shortcut editor extension, keyboard shortcuts can be removed as needed. Afterwards just append ”-c /path/to/folder” to the kiosk mode command line.
|
||
</p>
|
||
|
||
<p>
|
||
To restrict pages that can be opened, you can use a regular expression. The expression is a blacklist. To block undesirable sites you can do something like:
|
||
</p>
|
||
<pre class="code bash"><span class="re5">-b</span> <span class="st_h">'youtube|youporn'</span></pre>
|
||
|
||
<p>
|
||
By negating the expression you can also whitelist pages.
|
||
</p>
|
||
<pre class="code bash"><span class="re5">-b</span> <span class="st_h">'^(?!.*?(gmail|mail\.google|accounts\.google)).*'</span></pre>
|
||
|
||
<p>
|
||
Any links outside end up in an error page. All images and other files won't be loaded.
|
||
</p>
|
||
|
||
</div>
|
||
|
||
<h1 class="sectionedit14"><a name="proxy_servers" id="proxy_servers">Proxy servers</a></h1>
|
||
<div class="level1">
|
||
|
||
<p>
|
||
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.
|
||
</p>
|
||
|
||
</div>
|
||
|
||
<h4><a name="privoxy" id="privoxy">Privoxy</a></h4>
|
||
<div class="level4">
|
||
|
||
<p>
|
||
Privoxy is a non-caching web proxy with filter capabilites and particular support for blocking advertisements before even loading them.
|
||
</p>
|
||
|
||
<p>
|
||
<a href="http://www.privoxy.org/faq/" class="urlextern" title="http://www.privoxy.org/faq/" rel="nofollow">http://www.privoxy.org/faq/</a>
|
||
</p>
|
||
|
||
</div>
|
||
|
||
<h4><a name="mousehole" id="mousehole">Mousehole</a></h4>
|
||
<div class="level4">
|
||
|
||
<p>
|
||
Mousehole is a scriptable proxy server written in Ruby.
|
||
</p>
|
||
|
||
<p>
|
||
<a href="http://code.whytheluckystiff.net/mouseHole/" class="urlextern" title="http://code.whytheluckystiff.net/mouseHole/" rel="nofollow">http://code.whytheluckystiff.net/mouseHole/</a>
|
||
</p>
|
||
|
||
</div>
|
||
|
||
<h4><a name="polipo" id="polipo">Polipo</a></h4>
|
||
<div class="level4">
|
||
|
||
<p>
|
||
Polipo is a caching web proxy (a web cache) designed to be used by one
|
||
person or a small group of people. It is similar in spirit to WWWOFFLE, but
|
||
the implementation techniques are more like the ones used by Squid.
|
||
</p>
|
||
|
||
<p>
|
||
<a href="http://www.pps.jussieu.fr/~jch/software/polipo/" class="urlextern" title="http://www.pps.jussieu.fr/~jch/software/polipo/" rel="nofollow">http://www.pps.jussieu.fr/~jch/software/polipo/</a>
|
||
</p>
|
||
|
||
</div>
|
||
|
||
<h4><a name="are_socks_proxy_servers_supported" id="are_socks_proxy_servers_supported">Are SOCKS proxy servers supported?</a></h4>
|
||
<div class="level4">
|
||
|
||
<p>
|
||
The coming libSoup 2.40 will support SOCKS proxies, <a href="https://bugzilla.gnome.org/show_bug.cgi?id=553269" class="urlextern" title="https://bugzilla.gnome.org/show_bug.cgi?id=553269" rel="nofollow">see the relevant bug report</a>.
|
||
</p>
|
||
|
||
<p>
|
||
libSoup < 2.40 only supports <acronym title="Hyper Text Transfer Protocol">HTTP</acronym> proxy servers directly. A way to use SOCKS on Unix is to use tsocks with <acronym title="Secure Shell">SSH</acronym> as follows:
|
||
</p>
|
||
<ol>
|
||
<li class="level1"><div class="li"> Install 'tsocks'</div>
|
||
</li>
|
||
<li class="level1"><div class="li"> Open /etc/tsocks.conf in an editor</div>
|
||
</li>
|
||
<li class="level1"><div class="li"> Type something like this, you can choose the port freely: <pre class="code">server = 127.0.0.1
|
||
server_type = 5
|
||
server_port = 5555</pre>
|
||
</div>
|
||
</li>
|
||
<li class="level1"><div class="li"> Open an <acronym title="Secure Shell">SSH</acronym> connection with the same port: <pre class="code"> ssh -D localhost:5555 myhost.com </pre>
|
||
</div>
|
||
</li>
|
||
<li class="level1"><div class="li"> Run Midori with “tsocks” in front of it: <pre class="code"> tsocks midori </pre>
|
||
</div>
|
||
</li>
|
||
<li class="level1"><div class="li"> Now you can use for example <a href="http://www.whatsmyip.org/" class="urlextern" title="http://www.whatsmyip.org/" rel="nofollow">http://www.whatsmyip.org/</a> to verify that you are using a SOCKS connection. The IP address should match the one of your <acronym title="Secure Shell">SSH</acronym> host. Remember to keep the <acronym title="Secure Shell">SSH</acronym> login running, and don't suspend it, otherwise it won't work.</div>
|
||
</li>
|
||
<li class="level1"><div class="li"> If the connection fails for some reason, you should see a connection error.</div>
|
||
</li>
|
||
</ol>
|
||
|
||
</div>
|
||
|
||
<h1 class="sectionedit15"><a name="keyboard_hotkeys" id="keyboard_hotkeys">Keyboard Hotkeys</a></h1>
|
||
<div class="level1">
|
||
|
||
</div>
|
||
|
||
<h4><a name="hjkl" id="hjkl">HJKL</a></h4>
|
||
<div class="level4">
|
||
|
||
<p>
|
||
You can use the Vim-like key bindings [hjkl] to navigate a page. h=left j=down k=up l=right In a picture:
|
||
</p>
|
||
<pre class="code"> k
|
||
h l
|
||
j</pre>
|
||
|
||
<p>
|
||
You can also use the arrow keys to do the same.
|
||
</p>
|
||
|
||
</div>
|
||
|
||
<h4><a name="following_links" id="following_links">Following Links</a></h4>
|
||
<div class="level4">
|
||
|
||
<p>
|
||
To enable Hints in Midori, similar to vimperator in Firefox or xxxterm, press .
|
||
</p>
|
||
|
||
<p>
|
||
With hints enabled, type the link number, and press Enter to open the link in the current tab, or Ctrl-Enter to open the link in a new tab. To clear a typed link number before pressing Enter or Ctrl-Enter, use Escape.
|
||
</p>
|
||
|
||
</div>
|
||
|
||
<h4><a name="use_ctrl_shift_tab_to_switch_between_pages" id="use_ctrl_shift_tab_to_switch_between_pages">Use Ctrl(+Shift)+Tab to switch between pages</a></h4>
|
||
<div class="level4">
|
||
|
||
<p>
|
||
Since Midori 0.3.5 Ctrl+Tab is supported by default.
|
||
</p>
|
||
|
||
<p>
|
||
In older versions you can enable the History List extension under Tools → Extensions.
|
||
</p>
|
||
|
||
</div>
|
||
|
||
<h4><a name="customizing_keyboard_shortcuts" id="customizing_keyboard_shortcuts">Customizing keyboard shortcuts</a></h4>
|
||
<div class="level4">
|
||
|
||
<p>
|
||
Enable the Shortcuts extension Tools → Extensions. To edit a keybinding Tools → Customize Shortcuts…
|
||
</p>
|
||
|
||
</div>
|
||
|
||
<h4><a name="using_find" id="using_find">Using Find</a></h4>
|
||
<div class="level4">
|
||
|
||
<p>
|
||
Default shortcuts for Find are:
|
||
</p>
|
||
|
||
<p>
|
||
Find: Ctrl+f ”/” and ”,”<br/>
|
||
|
||
FindNext: Ctrl+g and Enter<br/>
|
||
|
||
FindPrevious: Shift+Ctrl+g<br/>
|
||
|
||
</p>
|
||
|
||
<p>
|
||
Dismissing Find:
|
||
</p>
|
||
|
||
<p>
|
||
When using Ctrl+f to bring up Find, use Ctrl+f again or ESC. When using ”/” or ”,” to bring up Find, the previous works here as well and by simply moving focus away from the Find box. For example: a Tab or a mouse click anywhere[besides links of course].
|
||
</p>
|
||
|
||
</div>
|
||
|
||
<h1 class="sectionedit16"><a name="mouse_gestures" id="mouse_gestures">Mouse Gestures</a></h1>
|
||
<div class="level1">
|
||
|
||
<p>
|
||
By default the right mouse button initiates gestures.
|
||
</p>
|
||
|
||
<p>
|
||
You can change the button using a hidden option:
|
||
</p>
|
||
<ol>
|
||
<li class="level1"><div class="li"> Create a text file ~/.config/midori/extensions/libmouse-gestures.so/config .</div>
|
||
</li>
|
||
<li class="level1"><div class="li"> Type the following in there:</div>
|
||
</li>
|
||
</ol>
|
||
<pre class="code"> [settings]
|
||
button=2</pre>
|
||
|
||
<p>
|
||
For a quick and dirty overview of the gestures in the current release take a look at the <a href="http://www.matthiaskruk.de/midori/mouse-gestures.pdf" class="urlextern" title="http://www.matthiaskruk.de/midori/mouse-gestures.pdf" rel="nofollow">preliminary manual</a>.
|
||
Further information is available at the <a href="http://www.matthiaskruk.de/midori" class="urlextern" title="http://www.matthiaskruk.de/midori" rel="nofollow">MGX website</a>.
|
||
</p>
|
||
|
||
<p>
|
||
Additionally, there are programs allowing mouse gestures system-wide, for example <a href="http://easystroke.wiki.sourceforge.net/" class="urlextern" title="http://easystroke.wiki.sourceforge.net/" rel="nofollow">EasyStroke</a>.
|
||
</p>
|
||
|
||
</div>
|
||
|
||
<h1 class="sectionedit17"><a name="user_scripts_and_styles" id="user_scripts_and_styles">User scripts and styles</a></h1>
|
||
<div class="level1">
|
||
|
||
<p>
|
||
UserScripts are scripts applied on some, or on all web pages. They can modify pages locally to add or alter functionality. That includes fixing bugs in web pages. User scripts are also available in other browsers, in the form of <a href="http://www.greasespot.net" class="urlextern" title="http://www.greasespot.net" rel="nofollow">Mozilla's Greasemonkey</a> or <a href="http://www.opera.com/support/tutorials/userjs/" class="urlextern" title="http://www.opera.com/support/tutorials/userjs/" rel="nofollow">Opera's User JavaScript</a>.
|
||
</p>
|
||
|
||
</div>
|
||
|
||
<h4><a name="how_to_install_a_userscript" id="how_to_install_a_userscript">How to install a UserScript</a></h4>
|
||
<div class="level4">
|
||
|
||
<p>
|
||
First enable the “User Addons” extension. It will show up as a “User Scripts” panel (and it also provides “User Styles”).
|
||
</p>
|
||
|
||
<p>
|
||
Now you need to find some scripts. You can find some at <a href="http://userscripts.org/" class="urlextern" title="http://userscripts.org/" rel="nofollow">userscripts.org</a>. Most scripts work fine, some may be written specifically for other browsers.
|
||
</p>
|
||
|
||
<p>
|
||
If you have Midori 0.3.0 or newer, you will be offered to install scripts as soon as you see them on the page.
|
||
</p>
|
||
|
||
<p>
|
||
To manually install a userscript, you have to download the script as a file, and put it in the folder <strong>~/.local/share/midori/scripts</strong>. You need to create that folder if it doesn't exist yet. Midori will automatically see and use it, which you can also see in the user scripts panel.
|
||
</p>
|
||
|
||
<p>
|
||
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.js where ”.js” is the extension.
|
||
</p>
|
||
|
||
</div>
|
||
|
||
<h4><a name="compatibility_with_greasemonkey" id="compatibility_with_greasemonkey">Compatibility with GreaseMonkey</a></h4>
|
||
<div class="level4">
|
||
|
||
<p>
|
||
As previously mentioned, Midori can use most scripts you will find. Midori supports Greasemonkey's <em>@include</em> and <em>@exclude</em> metadata so that scripts are only loaded on appropriate pages. Midori doesn't support advanced metadata, such as @require and @resource, so user scripts can't define dependencies on other scripts - most of the time this isn't a problem. Midori also does not support <a href="http://wiki.greasespot.net/API_reference" class="urlextern" title="http://wiki.greasespot.net/API_reference" rel="nofollow">Greasemonkey API</a>. Scripts must also be compatible with Webkit, since Midori is based on WebKit. A Greasemonkey script that makes use of functionality of Gecko/ Firefox will not work in Midori.
|
||
</p>
|
||
|
||
</div>
|
||
|
||
<h4><a name="flash_blocking_via_a_user_script" id="flash_blocking_via_a_user_script">Flash blocking via a User script</a></h4>
|
||
<div class="level4">
|
||
|
||
<p>
|
||
You can use <a href="http://userscripts.org/scripts/show/45343" class="urlextern" title="http://userscripts.org/scripts/show/45343" rel="nofollow">BlockFlash2</a> as a user script which replaces all Flash elements with a button that says “Play Flash”.
|
||
</p>
|
||
|
||
</div>
|
||
|
||
<h4><a name="flash_blocking_via_a_user_style" id="flash_blocking_via_a_user_style">Flash blocking via a User style</a></h4>
|
||
<div class="level4">
|
||
|
||
<p>
|
||
You can also use <a href="http://rightfootin.blogspot.com/2009/04/flashblock-wannabe.html" class="urlextern" title="http://rightfootin.blogspot.com/2009/04/flashblock-wannabe.html" rel="nofollow">FlashBlock WannaBe</a> as a user script in order to replace Flash elements with placeholders and load them on click. The script is pretty advanced compared to most Flash blockers found on the web.
|
||
</p>
|
||
|
||
</div>
|
||
|
||
<h2 class="sectionedit18"><a name="user_styles" id="user_styles">User styles</a></h2>
|
||
<div class="level2">
|
||
|
||
<p>
|
||
User styles are <acronym title="Cascading Style Sheets">CSS</acronym> 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.
|
||
</p>
|
||
|
||
</div>
|
||
|
||
<h4><a name="how_to_install_a_user_style" id="how_to_install_a_user_style">How to install a user style</a></h4>
|
||
<div class="level4">
|
||
|
||
<p>
|
||
First, you need to find some styles (or write your own). You can find some at <a href="http://userstyles.org/" class="urlextern" title="http://userstyles.org/" rel="nofollow">userstyles.org</a>. Many styles may or may not work, depending on whether the author decided to use browser specific features.
|
||
</p>
|
||
|
||
<p>
|
||
To install a user style, you have to download the style as a file, and put it in the following directory <strong>~/.local/share/midori/styles</strong> (you may need to create that directory if it does not exist). Midori will automatically see and use it, which you can also see in the user styles panel.
|
||
</p>
|
||
|
||
<p>
|
||
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.css where ”.css” is the extension.
|
||
</p>
|
||
|
||
</div>
|
||
|
||
<h4><a name="how_to_install_a_user_style_before_midori_0020" id="how_to_install_a_user_style_before_midori_0020">How to install a user style before Midori 0.0.20</a></h4>
|
||
<div class="level4">
|
||
|
||
<p>
|
||
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.
|
||
</p>
|
||
|
||
</div>
|
||
|
||
<h4><a name="a_user_css_to_display_the_url_when_a_link_is_hovered" id="a_user_css_to_display_the_url_when_a_link_is_hovered">A user css to display the url when a link is hovered</a></h4>
|
||
<div class="level4">
|
||
|
||
<p>
|
||
This user css is used to display the corresponding url when a link is hovered. This is similar to what chromium/chrome provides when hovering over a link, shown on the bottom left of the page. Add the following to <strong>~/.local/share/midori/styles</strong>, then restart Midori and make sure that it is enabled Tools → Userstyles.
|
||
</p>
|
||
|
||
<p>
|
||
Customize as needed:
|
||
</p>
|
||
<pre class="code">a[href]:hover {
|
||
text-decoration: none !important;
|
||
}
|
||
a[href]:hover:after {
|
||
content: attr(href);
|
||
position: fixed; left: 4px; bottom: 4px;
|
||
padding: 0 6px !important;
|
||
max-width: 95%; overflow: hidden;
|
||
white-space: nowrap; text-overflow: ellipsis;
|
||
font:10pt sans-serif !important; text-shadow: 0 0 12px white;
|
||
background-color: ButtonFace !important; color: ButtonText !important;
|
||
opacity: 0.8; outline: ButtonFace solid thick;
|
||
z-index: 9999;
|
||
}</pre>
|
||
|
||
</div>
|
||
<!-- EDIT16 SECTION "User styles" [18560-] --></div>
|
||
</body>
|
||
</html>
|