source: xsoft/graphweb/firefox.xml@ b47d633

11.1 lazarus trunk xry111/intltool xry111/test-20220226
Last change on this file since b47d633 was b47d633, checked in by Douglas R. Reno <renodr@…>, 7 months ago

Remove a bunch of dependencies on OpenJDK which are no longer valid.

  • Property mode set to 100644
File size: 24.2 KB
Line 
1<?xml version="1.0" encoding="ISO-8859-1"?>
2<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
3 "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
4 <!ENTITY % general-entities SYSTEM "../../general.ent">
5 %general-entities;
6
7 <!ENTITY firefox-download-http "&mozilla-http;/firefox/releases/&firefox-version;esr/source/firefox-&firefox-version;esr.source.tar.xz">
8 <!ENTITY firefox-download-ftp " ">
9 <!ENTITY firefox-md5sum "c6a45532322045ba54dad4b722a90f80">
10 <!ENTITY firefox-size "363 MB">
11 <!-- NB with stylo, much of the build uses rust, and therefore cargo files.
12 But the extra cached cargo files, if any, seem to be minimal -->
13 <!ENTITY firefox-buildsize "6.7 GB (195 MB installed) without tests">
14 <!-- editors: with ff63 and rust-1.29, ./mach build -j4 is probably the
15 most practical way to get a timing on a machine with more cores, if taking
16 cores offline is not practical. If in doubt, round up -->
17 <!ENTITY firefox-time "31 SBU (on a typical 4-core machine) without tests">
18]>
19
20<sect1 id="firefox" xreflabel="Firefox-&firefox-version;">
21 <?dbhtml filename="firefox.html" ?>
22
23 <sect1info>
24 <date>$Date$</date>
25 </sect1info>
26
27 <title>Firefox-&firefox-version;</title>
28
29 <indexterm zone="firefox">
30 <primary sortas="a-Firefox">Firefox</primary>
31 </indexterm>
32
33 <sect2 role="package">
34 <title>Introduction to Firefox</title>
35
36 <para>
37 <application>Firefox</application> is a stand-alone browser based on the
38 <application>Mozilla</application> codebase.
39 </para>
40
41 &lfs110a_checked;
42
43 <bridgehead renderas="sect3">Package Information</bridgehead>
44 <itemizedlist spacing="compact">
45 <listitem>
46 <para>
47 Download (HTTP): <ulink url="&firefox-download-http;"/>
48 </para>
49 </listitem>
50 <listitem>
51 <para>
52 Download (FTP): <ulink url="&firefox-download-ftp;"/>
53 </para>
54 </listitem>
55 <listitem>
56 <para>
57 Download MD5 sum: &firefox-md5sum;
58 </para>
59 </listitem>
60 <listitem>
61 <para>
62 Download size: &firefox-size;
63 </para>
64 </listitem>
65 <listitem>
66 <para>
67 Estimated disk space required: &firefox-buildsize;
68 </para>
69 </listitem>
70 <listitem>
71 <para>
72 Estimated build time: &firefox-time;
73 </para>
74 </listitem>
75 </itemizedlist>
76
77 <bridgehead renderas="sect3">Additional Downloads</bridgehead>
78 <itemizedlist spacing="compact">
79 <listitem>
80 <para>
81 Recommended patch:
82 <ulink url="&patch-root;/firefox-&firefox-version;esr-disable_rust_test-1.patch"/>
83 </para>
84 </listitem>
85 </itemizedlist>
86
87 <note>
88 <para>
89 The directory name is firefox-&firefox-version;
90 </para>
91
92 <para>
93 Extracting the tarball
94 will reset the permissions of the current directory to 0755 if you
95 have permission to do that. If you do this in a directory where
96 the sticky bit is set, such
97 as <filename class="directory">/tmp</filename> it will end with error
98 messages:
99 </para>
100
101<literallayout>tar: .: Cannot utime: Operation not permitted
102tar: .: Cannot change mode to rwxr-xr-t: Operation not permitted
103tar: Exiting with failure status due to previous errors
104</literallayout>
105
106 <para>
107 This does finish with non-zero status, but it does
108 <emphasis>NOT</emphasis> mean there is a real problem.
109 Do not untar as the <systemitem class="username">root</systemitem> user
110 in a directory where the sticky bit is set - that will unset it.
111 </para>
112
113 <para>
114 As with other large packages which use C++ (or rust), the SBU times
115 to build this vary more widely than you might expect. The build times
116 will increase significantly if your machine has to swap.
117 </para>
118
119 <!-- commented, by 78.0 it seems to work reliably
120 <para>
121 The mach build system (Python scripts) can be somewhat unreliable: if
122 the build fails and reports an Error, it can still return a status of
123 success, causing a scripted build to try to install (which does not rerun
124 the build), fail during the preparations for installing, but still exit
125 with a status of success. Also, on occasion it may limit itself to only
126 running one set of jobs - that will make the build take about 3 times as
127 long as running with four sets of jobs.
128 </para>-->
129
130 <para>
131 Although upstream prefer to use <application>PulseAudio</application>,
132 for the moment <application>Alsa</application> can still be used. Both
133 may need runtime configuration to get sound working.
134 </para>
135 </note>
136
137 <bridgehead renderas="sect3">Firefox Dependencies</bridgehead>
138
139 <bridgehead renderas="sect4">Required</bridgehead>
140 <para role="required">
141 <xref linkend="autoconf213"/>,
142 <xref linkend="cbindgen"/>,
143 <xref linkend="dbus-glib"/>,
144 both <xref linkend="gtk3"/> and
145 <xref linkend="gtk2"/>,
146 <xref linkend="libnotify"/>,
147 <xref linkend="llvm"/> (clang, used for bindgen even if using gcc),
148 <xref linkend="nodejs"/>,
149 <xref linkend="pulseaudio"/>
150 (or
151 <xref linkend="alsa-lib"/> if you edit the mozconfig;
152 now deprecated by mozilla), in either case please read the
153 Configuration Information,
154 <!-- rustc is required by cbindgen so not needed here
155 <xref linkend="rust"/>,-->
156 <xref linkend="python3"/> (rebuilt after installing <xref linkend="sqlite"/>),
157 <xref linkend="startup-notification"/>,
158 <xref linkend="unzip"/>,
159 <xref linkend="yasm"/>, and
160 <xref linkend="zip"/>
161 </para>
162
163 <bridgehead renderas="sect4">Recommended</bridgehead>
164 <para role="recommended">
165 <xref linkend="icu"/>,
166 <xref linkend="libevent"/>,
167 <xref linkend="libvpx"/>,
168 <xref linkend="libwebp"/>,
169 <xref linkend="nasm"/>,
170 <xref linkend="nss"/>
171 </para>
172
173 <note>
174 <para>
175 If you don't install recommended dependencies, then internal copies of
176 those packages will be used. They might be tested to work, but they can
177 be out of date or contain security holes.
178 </para>
179 </note>
180
181 <bridgehead renderas="sect4">Optional</bridgehead>
182 <para role="optional">
183 <xref linkend="curl"/>,
184 <xref linkend="doxygen"/>,
185 <xref role="runtime" linkend="ffmpeg"/> (runtime, to play mov, mp3 or mp4 files),
186 <!-- <phrase revision="sysv"><ulink url="https://sourceforge.net/projects/liboauth/files/">liboauth</ulink></phrase> -->
187 <xref linkend="liboauth"/>,
188 <!--<xref linkend="openjdk"/>, Not seen in logs -->
189 <xref linkend="valgrind"/>,
190 <xref linkend="wget"/>,
191 <xref linkend="wireless_tools"/>,
192 <ulink url="https://github.com/libproxy/libproxy">libproxy</ulink>
193 </para>
194
195 <para condition="html" role="usernotes">
196 User Notes: <ulink url="&blfs-wiki;/firefox"/>
197 </para>
198 </sect2>
199
200 <sect2 role="installation">
201 <title>Installation of Firefox</title>
202
203 <para>
204 The configuration of <application>Firefox</application> is accomplished
205 by creating a <filename>mozconfig</filename> file containing the desired
206 configuration options. A default <filename>mozconfig</filename> is
207 created below. To see the entire list of available configuration options
208 (and an abbreviated description of some of them), issue <command>./mach
209 configure &amp;&amp; ./configure --help | less</command>. You may also
210 wish to review the entire file and uncomment any other desired options.
211 Create the file by issuing the following command:
212 </para>
213
214<screen><userinput>cat &gt; mozconfig &lt;&lt; "EOF"
215<literal># If you have a multicore machine, all cores will be used by default.
216
217# If you have installed (or will install) wireless-tools, and you wish
218# to use geolocation web services, comment out this line
219ac_add_options --disable-necko-wifi
220
221# API Keys for geolocation APIs - necko-wifi (above) is required for MLS
222# Uncomment the following line if you wish to use Mozilla Location Service
223#ac_add_options --with-mozilla-api-keyfile=$PWD/mozilla-key
224
225# Uncomment the following line if you wish to use Google's geolocaton API
226# (needed for use with saved maps with Google Maps)
227#ac_add_options --with-google-location-service-api-keyfile=$PWD/google-key
228
229# startup-notification is required since firefox-78
230
231# Uncomment the following option if you have not installed PulseAudio
232#ac_add_options --disable-pulseaudio
233# or uncomment this if you installed alsa-lib instead of PulseAudio
234#ac_add_options --enable-alsa
235
236# Comment out following options if you have not installed
237# recommended dependencies:
238ac_add_options --with-system-icu
239ac_add_options --with-system-libevent
240ac_add_options --with-system-libvpx
241ac_add_options --with-system-nspr
242ac_add_options --with-system-nss
243ac_add_options --with-system-webp
244
245# Do not specify the gold linker which is not the default. It will take
246# longer and use more disk space when debug symbols are disabled.
247
248# libdavid (av1 decoder) requires nasm. Uncomment this if nasm
249# has not been installed.
250#ac_add_options --disable-av1
251
252# You cannot distribute the binary if you do this
253ac_add_options --enable-official-branding
254
255# Stripping is now enabled by default.
256# Uncomment these lines if you need to run a debugger:
257#ac_add_options --disable-strip
258#ac_add_options --disable-install-strip
259
260# Disabling debug symbols makes the build much smaller and a little
261# faster. Comment this if you need to run a debugger. Note: This is
262# required for compilation on i686.
263ac_add_options --disable-debug-symbols
264
265# The elf-hack is reported to cause failed installs (after successful builds)
266# on some machines. It is supposed to improve startup time and it shrinks
267# libxul.so by a few MB - comment this if you know your machine is not affected.
268ac_add_options --disable-elf-hack
269
270# The BLFS editors recommend not changing anything below this line:
271ac_add_options --prefix=/usr
272ac_add_options --enable-application=browser
273ac_add_options --disable-crashreporter
274ac_add_options --disable-updater
275# enabling the tests will use a lot more space and significantly
276# increase the build time, for no obvious benefit.
277ac_add_options --disable-tests
278
279# The default level of optimization again produces a working build with gcc.
280ac_add_options --enable-optimize
281
282ac_add_options --enable-system-ffi
283ac_add_options --enable-system-pixman
284
285ac_add_options --with-system-jpeg
286ac_add_options --with-system-png
287ac_add_options --with-system-zlib
288
289# The following option unsets Telemetry Reporting. With the Addons Fiasco,
290# Mozilla was found to be collecting user's data, including saved passwords and
291# web form data, without users consent. Mozilla was also found shipping updates
292# to systems without the user's knowledge or permission.
293# As a result of this, use the following command to permanently disable
294# telemetry reporting in Firefox.
295unset MOZ_TELEMETRY_REPORTING
296
297mk_add_options MOZ_OBJDIR=@TOPSRCDIR@/firefox-build-dir</literal>
298EOF</userinput></screen>
299
300 <para>
301 Compile <application>Firefox</application> by issuing the following
302 commands:
303 </para>
304
305 <para>
306 First apply a patch which works around unexplained failures on some machines
307 (a message that a python check on libgkrust.a identified 1 networking
308 function, getsockname) in the rust static library.
309 </para>
310
311<screen><userinput>patch -Np1 -i ../firefox-&firefox-version;esr-disable_rust_test-1.patch</userinput></screen>
312
313 <para>
314 If the geolocation APIs are needed:
315 </para>
316
317 <note>
318 <para>
319 <!-- Taken from Arch Linux - an immensely helpful link - Thanks -->
320 The Google and Mozilla API Keys below are specific to LFS. If using
321 these instructions for another distro, or if you intend to distribute
322 binary copies of the software using these instructions, please obtain
323 your own keys following the instructions located at
324 <ulink url="http://www.chromium.org/developers/how-tos/api-keys"/> and
325 <ulink url="https://location.services.mozilla.com/api"/> respectively.
326 <!-- BLFS Devs, register an account at Google with your
327 @linuxfromscratch.org email address, and I'll make you an administrator
328 for the 'Google APIs for LFS' project (where the API and OAuth keys
329 were created for use in the book).-->
330 </para>
331 </note>
332
333<screen><userinput>echo "AIzaSyDxKL42zsPjbke5O8_rPVpVrLrJ8aeE9rQ" > google-key
334echo "613364a7-9418-4c86-bcee-57e32fd70c23" > mozilla-key</userinput></screen>
335
336 <note>
337
338 <xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
339 href="../../xincludes/mozshm.xml"/>
340
341 <xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
342 href="../../xincludes/mozmach.xml"/>
343
344 </note>
345 <!--
346 <para>
347 If you are building on i686, apply a fix to prevent Internal Compiler
348 Errors in GCC-7+:
349 </para>
350
351<screen><userinput remap="pre">case $(uname -m) in
352 i?86) sed -i "562 s/mips64/i386/" gfx/skia/skia/third_party/skcms/src/Transform_inl.h ;;
353esac</userinput></screen>
354 -->
355<!--<para>
356 Apply a patch to allow this to be compiled with <xref linkend="rust"/>:
357 </para>
358
359<screen><userinput remap="pre">patch -p1 -i ../firefox-&firefox-version;esr-rustc1470-1.patch</userinput></screen>-->
360
361 <para>
362 Now invoke the Python <command>mach</command> script to compile the package.
363 </para>
364
365<screen><userinput>export CC=gcc CXX=g++ &amp;&amp;
366export MACH_USE_SYSTEM_PYTHON=1 &amp;&amp;
367export MOZBUILD_STATE_PATH=${PWD}/mozbuild &amp;&amp;
368./mach configure &amp;&amp;
369./mach build</userinput></screen>
370
371 <para>
372 The <filename>mozconfig</filename> above disables the tests because
373 they use a lot more time and disk space for no obvious benefit. If
374 you have nevertheless enabled them, you can run the tests by executing
375 <command>./mach gtest</command>. This will require a network connection,
376 and to be run from within an Xorg session - there is a popup dialog
377 when it fails to connect to ALSA (that does not create a failed test).
378 One or two tests will fail. To see the details of the failure(s) you
379 will need to log the output from that command so that you can review it.
380 </para>
381
382 <para>
383 Now, as the <systemitem class="username">root</systemitem> user:
384 </para>
385
386<screen role="root"><userinput>MACH_USE_SYSTEM_PYTHON=1 ./mach install</userinput></screen>
387
388 <para>
389 Empty the environment variables which were set above:
390 </para>
391
392<screen><userinput>unset CC CXX MACH_USE_SYSTEM_PYTHON MOZBUILD_STATE_PATH</userinput></screen>
393
394 </sect2>
395
396 <sect2 role="commands">
397 <title>Command Explanations</title>
398
399<!--<xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
400 href="../../xincludes/SIOCGSTAMP.xml"/>-->
401
402 <para>
403 <command>export CC=gcc CXX=g++ ...</command>: Upstream now prefer
404 <application>clang</application> so that they can use one compiler
405 everywhere. On the X86 architectures <application>clang</application>
406 now appears to support most of the same security-hardening options as
407 <application>GCC</application>.
408 <!-- supported in llvm-11
409 but the newer
410 <literal>-fstack-clash-protection</literal> is still not supported.-->
411 With the current versions and the default flags,
412 <application>GCC</application> creates a marginally bigger build but
413 takes typically 2 SBU less time on a 4-core machine using the mozconfig
414 above.
415 </para>
416
417 <para>
418 <command>export MOZBUILD_STATE_PATH=${PWD}/mozbuild</command>: The build
419 is now supposed to tell you that it intends to create <filename
420 class="directory">~/.mozbuild</filename>, and offer you an option to
421 press &lt;ENTER&gt; to accept this, or Ctrl-C to cancel and restart the
422 build after specifying the directory. In practice, the message may not
423 appear until after &lt;ENTER&gt; is keyed, i.e. the build stalls.
424 </para>
425
426 <para>
427 That directory is used for a (probably random) telemetry identifier.
428 Creating this in the build directory, and deleting that after the
429 installation, prevents it being used. If you wish to participate in
430 telemetry, export MOZBUILD_STATE_PATH to point to its default directory
431 and remove the entry from the <filename>mozconfig</filename>.
432 </para>
433
434 <para>
435 <command>MACH_USE_SYSTEM_PYTHON=1</command>: Use the system python
436 to create a virtual environment for <command>mach</command> without
437 downloading any python wheels.
438 </para>
439
440 <para>
441 <command>./mach configure</command>: This validates the supplied
442 dependencies and the <filename>mozconfig</filename>.
443 </para>
444
445 <para>
446 <option>./mach build --verbose</option>: Use this alternative if you
447 need details of which files are being compiled, together with any C or
448 C++ flags being used. But do not add '--verbose' to the install command,
449 it is not accepted there.
450 </para>
451
452 <para>
453 <option>./mach build -jN</option>: The build should, by default, use
454 all the online CPU cores. If using all the cores causes the build to swap
455 because you have insufficient memory, using fewer cores can be faster.
456 </para>
457
458<!--
459 <para>
460 <command>mkdir -pv /usr/lib/mozilla/plugins</command>: This ensures
461 that <filename class="directory">/usr/lib/mozilla/plugins/</filename>
462 exists.
463 </para>
464
465 <para>
466 <command>ln -sv ... /usr/lib/firefox/browser</command>:
467 This command creates a symbolic link to <filename
468 class="directory">/usr/lib/mozilla/plugins</filename>. It's not really
469 needed, as <application>Firefox</application> checks <filename
470 class="directory">/usr/lib/mozilla/plugins</filename> by default, but the
471 symbolic link is made to keep all the plugins installed in one folder.
472 </para>
473-->
474
475 </sect2>
476
477 <sect2 role="configuration">
478 <title>Configuring Firefox</title>
479
480 <para>
481 If you use a desktop environment like <application>Gnome</application> or
482 <application>KDE</application> you may like to create a
483 <filename>firefox.desktop</filename> file so that
484 <application>Firefox</application> appears in the panel's menus. <!--If you
485 didn't enable startup-notification in your mozconfig change the
486 StartupNotify line to false.--> As the
487 <systemitem class="username">root</systemitem> user:
488 </para>
489
490<screen role="root"><userinput>mkdir -pv /usr/share/applications &amp;&amp;
491mkdir -pv /usr/share/pixmaps &amp;&amp;
492
493MIMETYPE="text/xml;text/mml;text/html" &amp;&amp;
494MIMETYPE="$MIMETYPE;application/xhtml+xml;application/vnd.mozilla.xul+xml" &amp;&amp;
495MIMETYPE="$MIMETYPE;x-scheme-handler/http;x-scheme-handler/https" &amp;&amp;
496
497cat &gt; /usr/share/applications/firefox.desktop &lt;&lt; EOF &amp;&amp;
498<literal>[Desktop Entry]
499Encoding=UTF-8
500Name=Firefox Web Browser
501Comment=Browse the World Wide Web
502GenericName=Web Browser
503Exec=firefox %u
504Terminal=false
505Type=Application
506Icon=firefox
507Categories=GNOME;GTK;Network;WebBrowser;
508MimeType=$MIMETYPE
509StartupNotify=true</literal>
510EOF
511
512unset MIMETYPE &amp;&amp;
513
514ln -sfv /usr/lib/firefox/browser/chrome/icons/default/default128.png \
515 /usr/share/pixmaps/firefox.png</userinput></screen>
516
517 <sect3><title>Configuration Information</title>
518
519 <para>
520 The application settings for firefox are accessible by keying
521 <command>about:config</command> in the address bar.
522 </para>
523
524 <para>
525 Occasionally, getting working sound in
526 <application>firefox</application> can be a problem. Although upstream
527 prefers pulseaudio,
528 on balance using <application>Alsa</application> may be easier.
529 </para>
530
531 <para>
532 If you enabled <application>Alsa</application> for sound, you may need
533 to alter one variable to get working sound. If you run
534 <command>firefox</command> from a term and try to play something with
535 sound you might encounter error messages like:
536 </para>
537
538 <para>
539 <literal>Sandbox: seccomp sandbox violation: pid 3941, tid 4030,
540 syscall 16, args 48 2147767296 139909894784796 0 0 0.</literal>
541 </para>
542
543 <para>
544 That was on x86_64, on i686 the syscall number is 54. To allow this
545 syscall, in <command>about:config</command> change
546 <command>security.sandbox.content.syscall_whitelist</command> to 16
547 (or 54 if using i686).
548 </para>
549
550 <para>
551 If you use <command>pulseaudio</command> in a Desktop Environment, it
552 might already be started by that DE. But if it is not, although
553 firefox-57 managed to start it, firefox-58 did not. If you run
554 <command>firefox</command> from a term and this problem is present,
555 trying to play sound will
556 encounter error messages warning <literal>Can't get cubeb
557 context!</literal>
558 </para>
559
560 <para>
561 The fix for this is to close firefox, start pulseaudio to check it
562 does start (if not, read the information on Configuring in <xref
563 linkend="pulseaudio"/>) and restart firefox to check it is working.
564 If it now works, add the following to your <filename>~/.xinitrc</filename>:
565<phrase revision="sysv">
566<literal>pulseaudio --verbose --log-target=syslog&amp;</literal></phrase>
567<phrase revision="systemd">
568<literal>pulseaudio --verbose --log-target=journald&amp;</literal></phrase>
569 (unfortunately, on some systems this does not work).
570 </para>
571
572 <para>
573 You may wish to use multiple profiles within firefox. To do that, invoke
574 firefox as <command>firefox --ProfileManager</command>. You can also
575 check which profile is currently in use from
576 <command>about:profiles</command>.
577 </para>
578
579 <para>
580 Although WebRender (using the GPU for compositing) is not used by
581 default, it now appears to work well on supported hardware (ATI, Nvidia
582 and Intel GPUs with Mesa-18 or later. For an explanation, please see
583 <ulink
584 url="https://hacks.mozilla.org/2017/10/the-whole-web-at-maximum-fps-how-webrender-gets-rid-of-jank/">hacks.mozilla.org</ulink>.
585 The only downside seems to be that on a machine with limited RAM it might
586 use more RAM.
587 </para>
588
589 <para>
590 To check if WebRender is being used, look in about:support. In the Graphics
591 section Compositing will either show 'Basic' (i.e. not in use) or
592 'WebRender'. To enable it, go to about:config and change gfx.webrender.all
593 to True. You will need to restart firefox.
594 </para>
595
596 <para>
597 It may be useful to mention the processes from firefox which can appear in
598 <command>top</command> - as well as firefox itself, there may be multiple
599 Web Content processes, and now an RDD Process (Remote Data Decoder) which
600 appears when playing web videos encoded with av1 (libdav1d). If WebRender
601 has been enabled, a GPU Process will also appear when firefox has to
602 repaint (e.g. scrolling, opening a new tab, or playing a video).
603 </para>
604
605 </sect3>
606 </sect2>
607
608 <sect2 role="content">
609 <title>Contents</title>
610
611 <segmentedlist>
612 <segtitle>Installed Programs</segtitle>
613 <segtitle>Installed Libraries</segtitle>
614 <segtitle>Installed Directory</segtitle>
615
616 <seglistitem>
617 <seg>
618 firefox
619 </seg>
620 <seg>
621 Numerous libraries, browser components, plugins, extensions, and
622 helper modules installed in /usr/lib/firefox
623 </seg>
624 <seg>
625 /usr/lib/firefox and /usr/lib/mozilla
626 </seg>
627 </seglistitem>
628 </segmentedlist>
629
630 <variablelist>
631 <bridgehead renderas="sect3">Short Descriptions</bridgehead>
632 <?dbfo list-presentation="list"?>
633 <?dbhtml list-presentation="table"?>
634
635 <varlistentry id="firefox-prog">
636 <term><command>firefox</command></term>
637 <listitem>
638 <para>
639 is a <application>GTK+-3</application> internet browser that uses
640 the Mozilla Gecko rendering engine
641 </para>
642 <indexterm zone="firefox firefox-prog">
643 <primary sortas="b-firefox">firefox</primary>
644 </indexterm>
645 </listitem>
646 </varlistentry>
647
648 </variablelist>
649
650 </sect2>
651
652</sect1>
Note: See TracBrowser for help on using the repository browser.