Differences between version 77 and predecessor to the previous major change of MozillaNotes.
Other diffs: Previous Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 77 | Last edited on Tuesday, March 28, 2006 4:20:02 am | by SteveZobell | Revert |
| Older page: | version 67 | Last edited on Tuesday, January 17, 2006 11:22:57 am | by JohnMcPherson | Revert |
@@ -143,40 +143,47 @@
You can enable the flash plugin but not automatically load flash animations by using CSS and XUL.
This can also be used for arbitrary types.
-!Flash plugin click-to-load
+!
!Flash plugin click-to-load
Copy the following into your your <tt>$HOME/.mozilla/firefox/''salt''/chrome/userContent.css</tt> file:
<verbatim>
/* Prevent flash animations from playing until you click on them. */
- object[
[classid$=":D27CDB6E-AE6D-11cf-96B8-444553540000"],
- object[
[codebase*="swflash.cab"],
- object[
[type="application/x-shockwave-flash"],
- embed[
[type="application/x-shockwave-flash"],
+ object[classid$=":D27CDB6E-AE6D-11cf-96B8-444553540000"],
+ object[codebase*="swflash.cab"],
+ object[type="application/x-shockwave-flash"],
+ embed[type="application/x-shockwave-flash"],
embed[src$=".swf"]
- { -moz-binding: url("http
://www.cs.hmc.edu
/~jruderma
/clickToView.xml#ctv
"); }
+ { -moz-binding: url("resource
:///res
/clickToView.xml#flash
"); }
</verbatim>
The file location of the userContent.css will be different for other browsers: try <tt>$HOME/.galeon/mozilla/galeon/chrome</tt> or <tt>$HOME/.mozilla/default/''salt''/chrome/userContent.css</tt>.
-You can
copy the clickToView.xml file onto a local webserver as change
the url to point to your version
, if you don't want
to get it from his webserver every time
.
+Next,
copy the [
clickToView.xml | http://www.wlug.org.nz/archive/software/clickToView.xml ]
file into
the "res" subdirectory of the directory where firefox is installed. The command "which firefox" can help determine the directory where firefox is installed
, and root may be needed
to install the xml file. The xml file comments also give directions for installing clickToView, including hints for Windows OS users
.
-Unfortunately
the moz-binding must
be an http [URI];
file:// URIs don't
work due
to the security model
.
+clickToView.xml really should be in
the chrome directory with userContent.css, but this is not yet supported. Eventually, "profile:///chrome" may
be available to replace "resource:///res". And "
file:///" will not
work here. Keeping a copy of clickToView.xml in the chrome directory is a good idea anyway, and you may want to use a symlink
to the xml file in chrome from the res directory
.
+
+It is possible to load the clickToView.xml from the web instead of installing a local copy, but this can be slow and the xml file may not always be available or may be modified without your knowing. Use a local xml file if you can, but if necessary the file can be loaded from the web by replacing the moz-binding line with this:
+<verbatim>
+ { -moz-binding: url("http://www.wlug.org.nz/archive/software/clickToView.xml#flash"); }
+</verbatim>
There is also a Firefox extension called ~FlashBlock that does this, although it only works for recent versions of Firefox 1.4 or 1.5.
!! Java plugin click-to-load
You can prevent [Java] applets from loading immediately, requiring a click instead, by copying the following into your <tt>userContent.css</tt>:
<verbatim>
+/* Prevent java applets from playing until you click on them. */
object[codebase*="java"],
object[type="application/java"],
embed[type="application/java"],
applet[code$=".class"]
-{ -moz-binding: url("http
://www.cs.hmc.edu
/~jruderma
/clickToView.xml#ctv
"); }
+{ -moz-binding: url("resource
:///res
/clickToView.xml#java
"); }
</verbatim>
+As with the flash blocker above, [ clickToView.xml | http://www.wlug.org.nz/archive/software/clickToView.xml ] must be installed locally in the res subdirectory of the directory where Firefox is installed. Directions are also in the clickToView.xml file comments.
!!!Misc Neat Stuff
http://webfx.eae.net/games/minehunter/launcher.html
@@ -268,9 +275,39 @@
None, Up, Alt_L|Left
None, Down, Alt_L|Right
</verbatim>
-Finally, run 'imwheel -b 67' to map buttons 6 and 7 only. See Google or the IMWheel site for more examples.
--Pradeep Sanders
+Finally, run 'imwheel -b 67' to map buttons 6 and 7 only. See Google or the IMWheel site for more examples.
+
--Pradeep Sanders
+
+Another possibility is to remap the mouse buttons using xmodmap. This was actually done under Solaris (Nevada build 30), but I see no reason why it shouldn't also work under Linux (I don't currently have a Linux machine to try it).
+
+I discovered through trial and error (and a little luck) that buttons 6 and 7 were indeed making Mozilla move back and forward through the browsing history (I didn't actually have to do any of the above steps).
+
+Using xev to debug the mouse buttons (I have a Logitech MX700), I found the following:
+<verbatim>
+Button Desc
+1 Normal left button
+2 Press the wheel
+3 Normal right button
+4 Wheel up
+5 Wheel down
+6 Wheel up fast
+7 Wheel down fast
+8 Back thumb button
+9 Forward thumb button
+10 The one on the top
+11 Don't know
+</verbatim>
+
+6 and 7 are generated if the mouse wheel is spun very quickly, and they make Mozilla move through the browse history. Also, for some reason, the USB driver seems to detect 11 buttons - maybe it's a bug in the driver (but it doesn't seem to do any harm).
+
+Obviously, I'd like buttons 8 and 9 to make Mozilla move through the browse history, so I swapped them with buttons 6 and 7 using xmodmap:
+
+<verbatim>
+xmodmap -e "pointer = 1 2 3 4 5 8 9 6 7 10 11"
+</verbatim>
+-- Allan Black
!! Type-ahead Find Problems
I was having problems where somehow typeahead find would become enabled whenever I tried to type into the address bar and it was near on impossible to get out of the typeahead find mode. To disable it set
accessibility.typeaheadfind
