MozillaWiki - User contributions [en]

CA/Changing Trust Settings

2022-05-24T20:40:32Z

Kernst: /* Listing All Non-Default Root Certificate Settings */ include the 'sql:' part required for newer Mozilla products which have a cert9.db in SQLite format

This page describes how to change the default root certificate trust settings in Mozilla products, including Firefox and Thunderbird.

If you are seeing "Your connection is not secure" errors and you don't know why, visit [https://support.mozilla.org/en-US/kb/what-does-your-connection-is-not-secure-mean this support page].

Some browsers only display the root certificates that the user has actually used, and dynamically download new ones on demand. However, Mozilla believes it is important for users to know the root certificates that could be used, so the full set of certificates is always shown. This also allows you to edit the trust bits for any root certificates that you do not want to use.

== Important Warnings ==

Following instructions on this page may negatively affect your security and/or your browsing experience.

If you turn off the websites trust bit of a commonly used root certificate, you may get an "Your connection is not secure" error when you navigate to one or more popular websites. Bypassing such errors can be a security risk unless you know what you are doing. Therefore, it is strongly recommended that you '''note which root certificate you modify''', so that you can turn the trust bit back on if the change negatively impacts your browsing experience.

If you change the trust bits of a root certificate or add or delete roots, that change will be will '''not''' be affected by upgrading to newer versions of the software. It can only be changed again by you.

Deleting a root certificate that is in the default root store is equivalent to turning off all of the trust bits for that root. Therefore, '''even though the root certificate will re-appear in the Certificate Manager''', it will be treated as though you changed the trust bits of that root certificate to turn them all off.

== Trusting an Additional Root Certificate ==

The following describes how to manually import a root certificate into your installation of Firefox or other Mozilla products.

# Open the '''Options/Preferences''' window:
#* On Windows: Pull down the '''Tools''' menu and select '''Options…'''
#* On Mac: Pull down the '''Firefox''' menu and select '''Preferences...'''
#* On Linux: Pull down the '''Edit''' menu and select '''Preferences'''
# Select '''Privacy & Security'''
# Scroll down to the '''Certificates''' section
# Click on '''View Certificates..''' to open the '''Certificate Manager'''
# Select '''Authorities''' tab
#* Note: The root certificates with "Builtin Object Token" as the Security Device are the root certificates that are included by default in Mozilla products.
# Click on '''Import...'''
# Select the file of the Root Certificate that you want to import
# Select/Unselect the check-boxes indicating the trust bits, then click on '''OK'''
# Click on '''OK''' in the '''Certificate Manager'''
# Close the '''Options/Preferences''' tab

== Changing Root Certificate Trust Settings ==

To change the trust settings for root certificates in your installation of Firefox or other Mozilla products, follow the instructions above, except when you are in the Authorities tab of the Certificate Manager:

# Select the Root Certificate that you want to change
# Click on '''Edit Trust...'''
# Select/Unselect the check-boxes indicating the trust bits, then click on '''OK'''

Close and restart Firefox

== Deleting a Root Certificate ==

To delete a root certificate from your current instance of Firefox or other Mozilla products, follow the instructions above, except when you are in the Authorities tab of the Certificate Manager:

# Select the Root Certificate that you want to delete
# Click on '''Delete or Distrust...'''
# If you are sure you want to delete that root certificate, click on '''OK'''

Close and restart Firefox

== Restoring the Default Trust Settings for All Root Certificates ==
* [https://support.mozilla.org/en-US/kb/refresh-firefox-reset-add-ons-and-settings Refresh Firefox button] -- Recommended way to restore the security certificate settings.
* [https://support.mozilla.org/en-US/kb/what-does-your-connection-is-not-secure-mean#w_corrupted-certificate-store Manually restore the security certificate settings] -- only perform as last resort.

== Restoring the Default Trust Settings for a Single Root Certificate ==

If you want the cert to again respect any updates Mozilla makes to the default root store, this is extremely difficult. It is far easier to reset the entire store using the instructions above.

== Deeply Geeky Certificate Database Information ==

=== How Mozilla Products Respond to User Changes of Root Certificates ===

The following explains how Mozilla products behave when users change or delete root certificates.

For simplicity, the following assumes the basic and most common configuration, in which you have only the software distributed by Mozilla and do not have any
additional PKCS#11 modules (with or without any additional hardware) installed that may be capable of storing additional certificates. The model with them is slightly more complicated than the one described here.

[http://www.mozilla.org/projects/security/pki/nss/ Network Security Services (NSS)] is capable of accessing certificates that have been stored in a number
of places, all accessible through the PKCS#11 API. The two places of
greatest interest are

# Your certificate database, which is kept in a file on disk that you can alter. It starts out empty. Any root certificates it contains are there because of actions that you have taken, such as downloading or importing roots, or editing trust flags. As a rule, an update to your Mozilla installation of a Mozilla product will not change the contents of this database. (Rarely, it may change the FORMAT of the database, but not the content.)
# Mozilla's built-in root list, kept in a read-only shared library which is one of the files that gets updated whenever your product's executable files get updated.

Both of these stores of certificates may contain certificates and trust flags.

When NSS goes looking for a stored certificate, or trust flags for a stored certificate, it first looks in your certificate database. If it finds the certificate there, it stops. It uses whatever trust flags are there in that database with that certificate.

If it does NOT find the certificate it wants in that database, it looks in Mozilla's built-in root list. If it finds the cert there, then it uses the cert and trust flags it finds there. It does not copy the cert and flags from the built-in root list into your database. It just uses them where and as they are.

When you use your product's certificate manager to edit the trust flags on a certificate, the cert manager first looks for the cert in your database, and if it's there, then that copy gets edited. If it's not there, then cert manager looks for a copy in the built-in root list, and if found, copies it and its flags into your data base, and then edits it there. (After all, it cannot edit the copy in the built-in list, because that copy is read-only.) After that, that cert will remain in your database, and each time that the product goes looking for it, it will find it in your database, not in the built-in list.

If you delete a cert in your database that is also in the built-in list, it may appear to be completely gone, until you restart your program, at which point it will reappear, because it never left the built-in root list. However, the trust bits will be turned off for the root.

If you edit the trust on a cert in the root list, taking away (say) one of the 2 trust flags, but leaving the other one, then that cert and the single trust bit will be in your cert DB. After that, if Mozilla removes that cert completely from the built-in list, it will remain in your cert DB with the remaining trust flag. Mozilla's changes to the built-in list never affect your databases. Your databases contain what YOU put there. They're your changes, your responsibility.

In conclusion, the changes Mozilla makes to Mozilla's read-only list of built-in root certs affect only those certs that do not also appear in your cert DB. When you cause copies of any of those certs to appear in your cert DB, then you have taken control of the trust for those copies, and changes made by Mozilla thereafter to those certs will not affect you.

=== Restoring the Default Trust Bits for a Single Built-In Root Certificate ===

If you have edited the trust bits of a built-in root certificate, causing it to be copied to your personal database, you may wish to delete the copy from your database so that the default trust bits are again used. (Simply editing the trust bits to match the defaults would not give you the benefit of any updates Mozilla may later make to the defaults.) There is currently no UI to do this ({{bug|558222}}), but you can use the NSS <code>certutil</code> command-line tool. <code>certutil</code> does not ship with Mozilla products, and [https://groups.google.com/group/mozilla.dev.tech.crypto/browse_thread/thread/94d05b904280b6ed NSS itself does not have official binary releases at this time], but you can build <code>certutil</code> from source, or your OS distribution may include it (Fedora: <code>nss-tools</code>, Debian/Ubuntu: <code>libnss3-tools</code>).

To delete a certificate from your personal database:

# Note the Certificate Name as shown in the Certificate Manager.
# [https://support.mozilla.com/en-US/kb/profiles#w_how-do-i-find-my-profile Locate your profile].
# Shut down the Mozilla application.
# Run: <syntaxhighlight lang="bash"># for older Mozilla products, leave off the `sql:` part
certutil -d sql:PROFILE_DIR -D -n CERT_NAME</syntaxhighlight> substituting <tt>PROFILE_DIR</tt> with the path of your profile directory and <tt>CERT_NAME</tt> with the certificate name.
# Restart the Mozilla application.

=== Listing All Non-Default Root Certificate Settings ===

There is currently no UI to list all built-in root certificates for which you have overridden the default trust settings ({{bug|545498}}). However, you can use the <code>certutil</code> tool described in the previous section to list all the certificates in your personal database, which includes built-in root certificates whose trust you have changed along with added root certificates and many other kinds of certificates.

Run this command (doing it while the Mozilla application is running is probably unsupported but does not seem to cause problems in practice):

<syntaxhighlight lang="bash">
# for older Mozilla products, leave off the 'sql:' part
certutil -d sql:PROFILE_DIR -L
</syntaxhighlight>

where <tt>PROFILE_DIR</tt> is the path to your profile as noted above.

Root certificates will have trust fields of <code>c</code>, indicating a disabled trust bit, or <code>CT</code> or <code>C</code>, indicating an enabled trust bit. For example:

<pre>
Certificate Nickname Trust Attributes
SSL,S/MIME,JAR/XPI

My Favorite CA CT,c,c
Wiretaps R Us CA c,c,c
</pre>

CA/Changing Trust Settings

2022-05-24T20:39:07Z

Kernst: /* Restoring the Default Trust Bits for a Single Built-In Root Certificate */ syntax highlight

This page describes how to change the default root certificate trust settings in Mozilla products, including Firefox and Thunderbird.

If you are seeing "Your connection is not secure" errors and you don't know why, visit [https://support.mozilla.org/en-US/kb/what-does-your-connection-is-not-secure-mean this support page].

Some browsers only display the root certificates that the user has actually used, and dynamically download new ones on demand. However, Mozilla believes it is important for users to know the root certificates that could be used, so the full set of certificates is always shown. This also allows you to edit the trust bits for any root certificates that you do not want to use.

== Important Warnings ==

Following instructions on this page may negatively affect your security and/or your browsing experience.

If you turn off the websites trust bit of a commonly used root certificate, you may get an "Your connection is not secure" error when you navigate to one or more popular websites. Bypassing such errors can be a security risk unless you know what you are doing. Therefore, it is strongly recommended that you '''note which root certificate you modify''', so that you can turn the trust bit back on if the change negatively impacts your browsing experience.

If you change the trust bits of a root certificate or add or delete roots, that change will be will '''not''' be affected by upgrading to newer versions of the software. It can only be changed again by you.

Deleting a root certificate that is in the default root store is equivalent to turning off all of the trust bits for that root. Therefore, '''even though the root certificate will re-appear in the Certificate Manager''', it will be treated as though you changed the trust bits of that root certificate to turn them all off.

== Trusting an Additional Root Certificate ==

The following describes how to manually import a root certificate into your installation of Firefox or other Mozilla products.

# Open the '''Options/Preferences''' window:
#* On Windows: Pull down the '''Tools''' menu and select '''Options…'''
#* On Mac: Pull down the '''Firefox''' menu and select '''Preferences...'''
#* On Linux: Pull down the '''Edit''' menu and select '''Preferences'''
# Select '''Privacy & Security'''
# Scroll down to the '''Certificates''' section
# Click on '''View Certificates..''' to open the '''Certificate Manager'''
# Select '''Authorities''' tab
#* Note: The root certificates with "Builtin Object Token" as the Security Device are the root certificates that are included by default in Mozilla products.
# Click on '''Import...'''
# Select the file of the Root Certificate that you want to import
# Select/Unselect the check-boxes indicating the trust bits, then click on '''OK'''
# Click on '''OK''' in the '''Certificate Manager'''
# Close the '''Options/Preferences''' tab

== Changing Root Certificate Trust Settings ==

To change the trust settings for root certificates in your installation of Firefox or other Mozilla products, follow the instructions above, except when you are in the Authorities tab of the Certificate Manager:

# Select the Root Certificate that you want to change
# Click on '''Edit Trust...'''
# Select/Unselect the check-boxes indicating the trust bits, then click on '''OK'''

Close and restart Firefox

== Deleting a Root Certificate ==

To delete a root certificate from your current instance of Firefox or other Mozilla products, follow the instructions above, except when you are in the Authorities tab of the Certificate Manager:

# Select the Root Certificate that you want to delete
# Click on '''Delete or Distrust...'''
# If you are sure you want to delete that root certificate, click on '''OK'''

Close and restart Firefox

== Restoring the Default Trust Settings for All Root Certificates ==
* [https://support.mozilla.org/en-US/kb/refresh-firefox-reset-add-ons-and-settings Refresh Firefox button] -- Recommended way to restore the security certificate settings.
* [https://support.mozilla.org/en-US/kb/what-does-your-connection-is-not-secure-mean#w_corrupted-certificate-store Manually restore the security certificate settings] -- only perform as last resort.

== Restoring the Default Trust Settings for a Single Root Certificate ==

If you want the cert to again respect any updates Mozilla makes to the default root store, this is extremely difficult. It is far easier to reset the entire store using the instructions above.

== Deeply Geeky Certificate Database Information ==

=== How Mozilla Products Respond to User Changes of Root Certificates ===

The following explains how Mozilla products behave when users change or delete root certificates.

For simplicity, the following assumes the basic and most common configuration, in which you have only the software distributed by Mozilla and do not have any
additional PKCS#11 modules (with or without any additional hardware) installed that may be capable of storing additional certificates. The model with them is slightly more complicated than the one described here.

[http://www.mozilla.org/projects/security/pki/nss/ Network Security Services (NSS)] is capable of accessing certificates that have been stored in a number
of places, all accessible through the PKCS#11 API. The two places of
greatest interest are

# Your certificate database, which is kept in a file on disk that you can alter. It starts out empty. Any root certificates it contains are there because of actions that you have taken, such as downloading or importing roots, or editing trust flags. As a rule, an update to your Mozilla installation of a Mozilla product will not change the contents of this database. (Rarely, it may change the FORMAT of the database, but not the content.)
# Mozilla's built-in root list, kept in a read-only shared library which is one of the files that gets updated whenever your product's executable files get updated.

Both of these stores of certificates may contain certificates and trust flags.

When NSS goes looking for a stored certificate, or trust flags for a stored certificate, it first looks in your certificate database. If it finds the certificate there, it stops. It uses whatever trust flags are there in that database with that certificate.

If it does NOT find the certificate it wants in that database, it looks in Mozilla's built-in root list. If it finds the cert there, then it uses the cert and trust flags it finds there. It does not copy the cert and flags from the built-in root list into your database. It just uses them where and as they are.

When you use your product's certificate manager to edit the trust flags on a certificate, the cert manager first looks for the cert in your database, and if it's there, then that copy gets edited. If it's not there, then cert manager looks for a copy in the built-in root list, and if found, copies it and its flags into your data base, and then edits it there. (After all, it cannot edit the copy in the built-in list, because that copy is read-only.) After that, that cert will remain in your database, and each time that the product goes looking for it, it will find it in your database, not in the built-in list.

If you delete a cert in your database that is also in the built-in list, it may appear to be completely gone, until you restart your program, at which point it will reappear, because it never left the built-in root list. However, the trust bits will be turned off for the root.

If you edit the trust on a cert in the root list, taking away (say) one of the 2 trust flags, but leaving the other one, then that cert and the single trust bit will be in your cert DB. After that, if Mozilla removes that cert completely from the built-in list, it will remain in your cert DB with the remaining trust flag. Mozilla's changes to the built-in list never affect your databases. Your databases contain what YOU put there. They're your changes, your responsibility.

In conclusion, the changes Mozilla makes to Mozilla's read-only list of built-in root certs affect only those certs that do not also appear in your cert DB. When you cause copies of any of those certs to appear in your cert DB, then you have taken control of the trust for those copies, and changes made by Mozilla thereafter to those certs will not affect you.

=== Restoring the Default Trust Bits for a Single Built-In Root Certificate ===

If you have edited the trust bits of a built-in root certificate, causing it to be copied to your personal database, you may wish to delete the copy from your database so that the default trust bits are again used. (Simply editing the trust bits to match the defaults would not give you the benefit of any updates Mozilla may later make to the defaults.) There is currently no UI to do this ({{bug|558222}}), but you can use the NSS <code>certutil</code> command-line tool. <code>certutil</code> does not ship with Mozilla products, and [https://groups.google.com/group/mozilla.dev.tech.crypto/browse_thread/thread/94d05b904280b6ed NSS itself does not have official binary releases at this time], but you can build <code>certutil</code> from source, or your OS distribution may include it (Fedora: <code>nss-tools</code>, Debian/Ubuntu: <code>libnss3-tools</code>).

To delete a certificate from your personal database:

# Note the Certificate Name as shown in the Certificate Manager.
# [https://support.mozilla.com/en-US/kb/profiles#w_how-do-i-find-my-profile Locate your profile].
# Shut down the Mozilla application.
# Run: <syntaxhighlight lang="bash"># for older Mozilla products, leave off the `sql:` part
certutil -d sql:PROFILE_DIR -D -n CERT_NAME</syntaxhighlight> substituting <tt>PROFILE_DIR</tt> with the path of your profile directory and <tt>CERT_NAME</tt> with the certificate name.
# Restart the Mozilla application.

=== Listing All Non-Default Root Certificate Settings ===

There is currently no UI to list all built-in root certificates for which you have overridden the default trust settings ({{bug|545498}}). However, you can use the <code>certutil</code> tool described in the previous section to list all the certificates in your personal database, which includes built-in root certificates whose trust you have changed along with added root certificates and many other kinds of certificates.

Run this command (doing it while the Mozilla application is running is probably unsupported but does not seem to cause problems in practice):

certutil -d ''PROFILE_DIR'' -L

Root certificates will have trust fields of <code>c</code>, indicating a disabled trust bit, or <code>CT</code> or <code>C</code>, indicating an enabled trust bit. For example:

<pre>
Certificate Nickname Trust Attributes
SSL,S/MIME,JAR/XPI

My Favorite CA CT,c,c
Wiretaps R Us CA c,c,c
</pre>

CA/Changing Trust Settings

2022-05-24T20:38:44Z

Kernst: /* Restoring the Default Trust Bits for a Single Built-In Root Certificate */ update to work with 'cert9.db' which requires 'sql:' prefix, otherwise you get an error

This page describes how to change the default root certificate trust settings in Mozilla products, including Firefox and Thunderbird.

If you are seeing "Your connection is not secure" errors and you don't know why, visit [https://support.mozilla.org/en-US/kb/what-does-your-connection-is-not-secure-mean this support page].

Some browsers only display the root certificates that the user has actually used, and dynamically download new ones on demand. However, Mozilla believes it is important for users to know the root certificates that could be used, so the full set of certificates is always shown. This also allows you to edit the trust bits for any root certificates that you do not want to use.

== Important Warnings ==

Following instructions on this page may negatively affect your security and/or your browsing experience.

If you turn off the websites trust bit of a commonly used root certificate, you may get an "Your connection is not secure" error when you navigate to one or more popular websites. Bypassing such errors can be a security risk unless you know what you are doing. Therefore, it is strongly recommended that you '''note which root certificate you modify''', so that you can turn the trust bit back on if the change negatively impacts your browsing experience.

If you change the trust bits of a root certificate or add or delete roots, that change will be will '''not''' be affected by upgrading to newer versions of the software. It can only be changed again by you.

Deleting a root certificate that is in the default root store is equivalent to turning off all of the trust bits for that root. Therefore, '''even though the root certificate will re-appear in the Certificate Manager''', it will be treated as though you changed the trust bits of that root certificate to turn them all off.

== Trusting an Additional Root Certificate ==

The following describes how to manually import a root certificate into your installation of Firefox or other Mozilla products.

# Open the '''Options/Preferences''' window:
#* On Windows: Pull down the '''Tools''' menu and select '''Options…'''
#* On Mac: Pull down the '''Firefox''' menu and select '''Preferences...'''
#* On Linux: Pull down the '''Edit''' menu and select '''Preferences'''
# Select '''Privacy & Security'''
# Scroll down to the '''Certificates''' section
# Click on '''View Certificates..''' to open the '''Certificate Manager'''
# Select '''Authorities''' tab
#* Note: The root certificates with "Builtin Object Token" as the Security Device are the root certificates that are included by default in Mozilla products.
# Click on '''Import...'''
# Select the file of the Root Certificate that you want to import
# Select/Unselect the check-boxes indicating the trust bits, then click on '''OK'''
# Click on '''OK''' in the '''Certificate Manager'''
# Close the '''Options/Preferences''' tab

== Changing Root Certificate Trust Settings ==

To change the trust settings for root certificates in your installation of Firefox or other Mozilla products, follow the instructions above, except when you are in the Authorities tab of the Certificate Manager:

# Select the Root Certificate that you want to change
# Click on '''Edit Trust...'''
# Select/Unselect the check-boxes indicating the trust bits, then click on '''OK'''

Close and restart Firefox

== Deleting a Root Certificate ==

To delete a root certificate from your current instance of Firefox or other Mozilla products, follow the instructions above, except when you are in the Authorities tab of the Certificate Manager:

# Select the Root Certificate that you want to delete
# Click on '''Delete or Distrust...'''
# If you are sure you want to delete that root certificate, click on '''OK'''

Close and restart Firefox

== Restoring the Default Trust Settings for All Root Certificates ==
* [https://support.mozilla.org/en-US/kb/refresh-firefox-reset-add-ons-and-settings Refresh Firefox button] -- Recommended way to restore the security certificate settings.
* [https://support.mozilla.org/en-US/kb/what-does-your-connection-is-not-secure-mean#w_corrupted-certificate-store Manually restore the security certificate settings] -- only perform as last resort.

== Restoring the Default Trust Settings for a Single Root Certificate ==

If you want the cert to again respect any updates Mozilla makes to the default root store, this is extremely difficult. It is far easier to reset the entire store using the instructions above.

== Deeply Geeky Certificate Database Information ==

=== How Mozilla Products Respond to User Changes of Root Certificates ===

The following explains how Mozilla products behave when users change or delete root certificates.

For simplicity, the following assumes the basic and most common configuration, in which you have only the software distributed by Mozilla and do not have any
additional PKCS#11 modules (with or without any additional hardware) installed that may be capable of storing additional certificates. The model with them is slightly more complicated than the one described here.

[http://www.mozilla.org/projects/security/pki/nss/ Network Security Services (NSS)] is capable of accessing certificates that have been stored in a number
of places, all accessible through the PKCS#11 API. The two places of
greatest interest are

# Your certificate database, which is kept in a file on disk that you can alter. It starts out empty. Any root certificates it contains are there because of actions that you have taken, such as downloading or importing roots, or editing trust flags. As a rule, an update to your Mozilla installation of a Mozilla product will not change the contents of this database. (Rarely, it may change the FORMAT of the database, but not the content.)
# Mozilla's built-in root list, kept in a read-only shared library which is one of the files that gets updated whenever your product's executable files get updated.

Both of these stores of certificates may contain certificates and trust flags.

When NSS goes looking for a stored certificate, or trust flags for a stored certificate, it first looks in your certificate database. If it finds the certificate there, it stops. It uses whatever trust flags are there in that database with that certificate.

If it does NOT find the certificate it wants in that database, it looks in Mozilla's built-in root list. If it finds the cert there, then it uses the cert and trust flags it finds there. It does not copy the cert and flags from the built-in root list into your database. It just uses them where and as they are.

When you use your product's certificate manager to edit the trust flags on a certificate, the cert manager first looks for the cert in your database, and if it's there, then that copy gets edited. If it's not there, then cert manager looks for a copy in the built-in root list, and if found, copies it and its flags into your data base, and then edits it there. (After all, it cannot edit the copy in the built-in list, because that copy is read-only.) After that, that cert will remain in your database, and each time that the product goes looking for it, it will find it in your database, not in the built-in list.

If you delete a cert in your database that is also in the built-in list, it may appear to be completely gone, until you restart your program, at which point it will reappear, because it never left the built-in root list. However, the trust bits will be turned off for the root.

If you edit the trust on a cert in the root list, taking away (say) one of the 2 trust flags, but leaving the other one, then that cert and the single trust bit will be in your cert DB. After that, if Mozilla removes that cert completely from the built-in list, it will remain in your cert DB with the remaining trust flag. Mozilla's changes to the built-in list never affect your databases. Your databases contain what YOU put there. They're your changes, your responsibility.

In conclusion, the changes Mozilla makes to Mozilla's read-only list of built-in root certs affect only those certs that do not also appear in your cert DB. When you cause copies of any of those certs to appear in your cert DB, then you have taken control of the trust for those copies, and changes made by Mozilla thereafter to those certs will not affect you.

=== Restoring the Default Trust Bits for a Single Built-In Root Certificate ===

If you have edited the trust bits of a built-in root certificate, causing it to be copied to your personal database, you may wish to delete the copy from your database so that the default trust bits are again used. (Simply editing the trust bits to match the defaults would not give you the benefit of any updates Mozilla may later make to the defaults.) There is currently no UI to do this ({{bug|558222}}), but you can use the NSS <code>certutil</code> command-line tool. <code>certutil</code> does not ship with Mozilla products, and [https://groups.google.com/group/mozilla.dev.tech.crypto/browse_thread/thread/94d05b904280b6ed NSS itself does not have official binary releases at this time], but you can build <code>certutil</code> from source, or your OS distribution may include it (Fedora: <code>nss-tools</code>, Debian/Ubuntu: <code>libnss3-tools</code>).

To delete a certificate from your personal database:

# Note the Certificate Name as shown in the Certificate Manager.
# [https://support.mozilla.com/en-US/kb/profiles#w_how-do-i-find-my-profile Locate your profile].
# Shut down the Mozilla application.
# Run: <syntaxhighlight># for older Mozilla products, leave off the `sql:` part
certutil -d sql:PROFILE_DIR -D -n CERT_NAME</syntaxhighlight> substituting <tt>PROFILE_DIR</tt> with the path of your profile directory and <tt>CERT_NAME</tt> with the certificate name.
# Restart the Mozilla application.

=== Listing All Non-Default Root Certificate Settings ===

There is currently no UI to list all built-in root certificates for which you have overridden the default trust settings ({{bug|545498}}). However, you can use the <code>certutil</code> tool described in the previous section to list all the certificates in your personal database, which includes built-in root certificates whose trust you have changed along with added root certificates and many other kinds of certificates.

Run this command (doing it while the Mozilla application is running is probably unsupported but does not seem to cause problems in practice):

certutil -d ''PROFILE_DIR'' -L

Root certificates will have trust fields of <code>c</code>, indicating a disabled trust bit, or <code>CT</code> or <code>C</code>, indicating an enabled trust bit. For example:

<pre>
Certificate Nickname Trust Attributes
SSL,S/MIME,JAR/XPI

My Favorite CA CT,c,c
Wiretaps R Us CA c,c,c
</pre>

Fennec/NativeUI/UserExperience/ReaderMode

2012-06-28T19:36:43Z

Kernst: /* Favorites 2 by Matt Gemmell */

Below is the proposed first version of a reader mode for mobile Firefox.
* All the mockups (some old) can found in this [http://www.flickr.com/photos/patrykdesign/sets/72157628389027877/ Flickr folder].
* Bug [http://bugzilla.mozilla.org/show_bug.cgi?id=750678 #750678] is related to reading list navigation (and may end up implementing some of the mockups below).
* Other reader mode bugs are tracked by [https://bugzilla.mozilla.org/show_bug.cgi?id=696921 #696921] and [http://lucasr.org/2012/06/21/reader-mode-in-firefox-mobile/ this blog post] shows screenshots of an early UI implementation from June 2012. 
==User Interaction==
===1. How to Access Reader Mode from the Browser?===
Problem: The new browser design is heading towards a chromeless / buttonless aesthetic, how do we introduce the reader mode? 
Solution: The reader mode can hidden the the menu invoked by pressing the hardware/software menu button or with an icon which appears in the URL bar. In tablets there is another possible interaction: it would be interesting to have a feature (perhaps ON by default) where when you rotate the device from landscape to portrait the page would automatically enter reader mode. 
https://farm8.staticflickr.com/7017/6560941471_5153493ffa_b.jpg 
[http://www.flickr.com/photos/patrykdesign/6560941471/in/set-72157628389027877/ Proposed Visual Design Mock Up]
 

===2. Proposed Interactions===
Problem: Add functionality to the reader mode while still maintaining a chromeless, reading focused layout. 
Solution: Introduce off screen menus rendered visible with swiping gestures. 
https://farm8.staticflickr.com/7008/6517216455_d480da0ea1_b.jpg 
[http://www.flickr.com/photos/patrykdesign/6517216455/in/set-72157628389027877 Sample Interaction Flow] 
https://farm8.staticflickr.com/7166/6560945787_f996192027_b.jpg 
[http://www.flickr.com/photos/patrykdesign/6560945787/in/set-72157628389027877 Proposed Visual Design Mock Up] 
https://farm8.staticflickr.com/7015/6589809399_8a96004c7d_b.jpg 
[http://www.flickr.com/photos/patrykdesign/6589809399/in/photostream Examples of Article Navigation (Potentially for a future release)]
 

===3. The Toolbar===
Problem: How do we access / display the various options without intruding on the reading experience 
Solution: On tapping of the screen a translucent tool bar appears, further options can be invoked by pressing the menu icon in the bar, or the hardware menu key. 
https://farm8.staticflickr.com/7202/6964642207_bdcff2b041_b.jpg 
[http://www.flickr.com/photos/patrykdesign/6964642207/in/photostream Proposed Visual Design Mock Up]
 

===4. Visual Variations===
Various Examples: 
https://farm8.staticflickr.com/7149/6560944301_67bccaaee8_b.jpg 
[http://www.flickr.com/photos/patrykdesign/6560944301/in/photostream/ Overall Layout & Typography, Sans Serifs will likely be Open Sans as seen in the later mock ups] 
https://farm8.staticflickr.com/7147/6560942271_dd0e2d08fe_b.jpg 
[http://www.flickr.com/photos/patrykdesign/6560942271/in/photostream/ Colour Themes] 
https://farm8.staticflickr.com/7145/6560945017_c71c0b0b7b_b.jpg 
[http://www.flickr.com/photos/patrykdesign/6560945017/in/photostream/ Image Treatement, ideally if we could aim for the left example, flush layout.]
 

===5. Scalability===
https://farm8.staticflickr.com/7051/6964643319_6224330a9b_b.jpg 
[http://www.flickr.com/photos/patrykdesign/6560940929/in/photostream/ Typography size scaling ratio pairs, we will need to create different ones for 7" and 10" tablets] 
https://farm8.staticflickr.com/7194/6821932828_7aeda656c3_b.jpg 
[http://www.flickr.com/photos/patrykdesign/6821932828/in/photostream Phone to Tablet scaling, notice titles and picture location is different, we will need custom settings for various form factors] 
https://farm8.staticflickr.com/7195/6964642677_73c976d66f_b.jpg 
10.1" Tablet, looks great in portrait 
https://farm8.staticflickr.com/7180/6964642743_71b50a0794_b.jpg 
A bit awkward in landscape, but ok for v.1 
https://farm8.staticflickr.com/7197/6964642807_a12551d989_b.jpg 
Perhaps we can add images or article scroll menu in landscape to maximize the space? v.1 would be nice, but if not v.2? 

==Discoverability==
Early [https://bugzilla.mozilla.org/show_bug.cgi?id=696921#c6 user feedback] in bug [https://bugzilla.mozilla.org/show_bug.cgi?id=696921 696921] suggests that discoverability may be an issue. One way to alleviate this might be to create a "first-launch" help screen for Fennec. Attached are some examples of prior art (mostly iOS apps, with links to source) for such help screens. Some first-use help is implemented as a "walkthrough" with several steps, or even a "play-through" animation. Others have shaded overlays with callouts describing the various UI elements, or make use of the blank area within the app's "home" screen to highlight elements of the UI.

===First-Launch Help Screens: Prior Art===

====The [http://tapbots.com Tapbots] iOS apps====
These apps have very intuitive first-launch help screens which introduce new users to UI controls and gestures. The Convertbot app even has a "play-through" animated demonstration of the app's features.

[[File:Tweetbot first-launch help.png|thumb|200px|left|First launch help for Tapbot's [http://tapbots.com/software/tweetbot/ Tweetbot] app for iOS, showing swipe gestures.]][[File:Convertbot first-launch help.png|thumb|200px|none|The first launch help for [http://tapbots.com/software/convertbot/ Convertbot] is an animated "play-through."]]
{{clear}}

====[http://instinctivecode.com/favorites/ Favorites 2] by Matt Gemmell====
When the app is first launched, the empty speed dial screen shows this help:

[[File:MattGemmell Favorites2 UI.jpg|thumb|200px|none|First launch help for the [http://instinctivecode.com/favorites/ Favorites] iOS app invites users to add new favorites by directing them to the appropriate UI widget.]]
{{clear}}

====[http://sophiestication.com/articles/ Articles] by Sophia Teutschler====
This is another app with a very minimalist UI, like Fennec. When no articles are open within the app, a callout directs the user to the search bar at the top of the screen.

[[File:Articles first-launch help.png|thumb|200px|none|First-launch help for Sophiestication's [http://sophiestication.com/articles/ Articles] iOS app.]]
{{clear}}

Fennec/NativeUI/UserExperience/ReaderMode

2012-06-28T19:33:02Z

Kernst: /* Discoverability */

Below is the proposed first version of a reader mode for mobile Firefox.
* All the mockups (some old) can found in this [http://www.flickr.com/photos/patrykdesign/sets/72157628389027877/ Flickr folder].
* Bug [http://bugzilla.mozilla.org/show_bug.cgi?id=750678 #750678] is related to reading list navigation (and may end up implementing some of the mockups below).
* Other reader mode bugs are tracked by [https://bugzilla.mozilla.org/show_bug.cgi?id=696921 #696921] and [http://lucasr.org/2012/06/21/reader-mode-in-firefox-mobile/ this blog post] shows screenshots of an early UI implementation from June 2012. 
==User Interaction==
===1. How to Access Reader Mode from the Browser?===
Problem: The new browser design is heading towards a chromeless / buttonless aesthetic, how do we introduce the reader mode? 
Solution: The reader mode can hidden the the menu invoked by pressing the hardware/software menu button or with an icon which appears in the URL bar. In tablets there is another possible interaction: it would be interesting to have a feature (perhaps ON by default) where when you rotate the device from landscape to portrait the page would automatically enter reader mode. 
https://farm8.staticflickr.com/7017/6560941471_5153493ffa_b.jpg 
[http://www.flickr.com/photos/patrykdesign/6560941471/in/set-72157628389027877/ Proposed Visual Design Mock Up]
 

===2. Proposed Interactions===
Problem: Add functionality to the reader mode while still maintaining a chromeless, reading focused layout. 
Solution: Introduce off screen menus rendered visible with swiping gestures. 
https://farm8.staticflickr.com/7008/6517216455_d480da0ea1_b.jpg 
[http://www.flickr.com/photos/patrykdesign/6517216455/in/set-72157628389027877 Sample Interaction Flow] 
https://farm8.staticflickr.com/7166/6560945787_f996192027_b.jpg 
[http://www.flickr.com/photos/patrykdesign/6560945787/in/set-72157628389027877 Proposed Visual Design Mock Up] 
https://farm8.staticflickr.com/7015/6589809399_8a96004c7d_b.jpg 
[http://www.flickr.com/photos/patrykdesign/6589809399/in/photostream Examples of Article Navigation (Potentially for a future release)]
 

===3. The Toolbar===
Problem: How do we access / display the various options without intruding on the reading experience 
Solution: On tapping of the screen a translucent tool bar appears, further options can be invoked by pressing the menu icon in the bar, or the hardware menu key. 
https://farm8.staticflickr.com/7202/6964642207_bdcff2b041_b.jpg 
[http://www.flickr.com/photos/patrykdesign/6964642207/in/photostream Proposed Visual Design Mock Up]
 

===4. Visual Variations===
Various Examples: 
https://farm8.staticflickr.com/7149/6560944301_67bccaaee8_b.jpg 
[http://www.flickr.com/photos/patrykdesign/6560944301/in/photostream/ Overall Layout & Typography, Sans Serifs will likely be Open Sans as seen in the later mock ups] 
https://farm8.staticflickr.com/7147/6560942271_dd0e2d08fe_b.jpg 
[http://www.flickr.com/photos/patrykdesign/6560942271/in/photostream/ Colour Themes] 
https://farm8.staticflickr.com/7145/6560945017_c71c0b0b7b_b.jpg 
[http://www.flickr.com/photos/patrykdesign/6560945017/in/photostream/ Image Treatement, ideally if we could aim for the left example, flush layout.]
 

===5. Scalability===
https://farm8.staticflickr.com/7051/6964643319_6224330a9b_b.jpg 
[http://www.flickr.com/photos/patrykdesign/6560940929/in/photostream/ Typography size scaling ratio pairs, we will need to create different ones for 7" and 10" tablets] 
https://farm8.staticflickr.com/7194/6821932828_7aeda656c3_b.jpg 
[http://www.flickr.com/photos/patrykdesign/6821932828/in/photostream Phone to Tablet scaling, notice titles and picture location is different, we will need custom settings for various form factors] 
https://farm8.staticflickr.com/7195/6964642677_73c976d66f_b.jpg 
10.1" Tablet, looks great in portrait 
https://farm8.staticflickr.com/7180/6964642743_71b50a0794_b.jpg 
A bit awkward in landscape, but ok for v.1 
https://farm8.staticflickr.com/7197/6964642807_a12551d989_b.jpg 
Perhaps we can add images or article scroll menu in landscape to maximize the space? v.1 would be nice, but if not v.2? 

==Discoverability==
Early [https://bugzilla.mozilla.org/show_bug.cgi?id=696921#c6 user feedback] in bug [https://bugzilla.mozilla.org/show_bug.cgi?id=696921 696921] suggests that discoverability may be an issue. One way to alleviate this might be to create a "first-launch" help screen for Fennec. Attached are some examples of prior art (mostly iOS apps, with links to source) for such help screens. Some first-use help is implemented as a "walkthrough" with several steps, or even a "play-through" animation. Others have shaded overlays with callouts describing the various UI elements, or make use of the blank area within the app's "home" screen to highlight elements of the UI.

===First-Launch Help Screens: Prior Art===

====The [http://tapbots.com Tapbots] iOS apps====
These apps have very intuitive first-launch help screens which introduce new users to UI controls and gestures. The Convertbot app even has a "play-through" animated demonstration of the app's features.

[[File:Tweetbot first-launch help.png|thumb|200px|left|First launch help for Tapbot's [http://tapbots.com/software/tweetbot/ Tweetbot] app for iOS, showing swipe gestures.]][[File:Convertbot first-launch help.png|thumb|200px|none|The first launch help for [http://tapbots.com/software/convertbot/ Convertbot] is an animated "play-through."]]
{{clear}}

====[http://instinctivecode.com/favorites/ Favorites 2] by Matt Gemmell====
When the app is first launched, the empty speed dial screen shows this help:

[[File:MattGemmell Favorites2 UI.jpg|thumb|200px|none|First launch help for the [http://instinctivecode.com/favorites/ Favorites] iOS app]]
{{clear}}

====[http://sophiestication.com/articles/ Articles] by Sophia Teutschler====
This is another app with a very minimalist UI, like Fennec. When no articles are open within the app, a callout directs the user to the search bar at the top of the screen.

[[File:Articles first-launch help.png|thumb|200px|none|First-launch help for Sophiestication's [http://sophiestication.com/articles/ Articles] iOS app.]]
{{clear}}

User:Kernst/Sandbox

2012-06-28T16:56:22Z

Kernst:

<div class="divContainerMain">
<h3>
Up Side Callout</h3>
<div>
Ramesh Soni Said</div>
<div class="calloutUp">
<div class="calloutUp2">
</div>
</div>
<div class="divContainerUp">
Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Aliquam dignissim tincidunt
turpis. Mauris pede. Vestibulum gravida magna id nibh. In nec urna. Sed ut purus.
Duis sit amet lacus ornare massa mattis consequat. Donec nec tellus. Nam quis nulla
viverra diam faucibus dictum. Nulla facilisi. Donec sit amet dolor at sapien accumsan
consectetuer.
</div>
 
 
<h3>
Down Side Callout</h3>
<div class="divContainerDown">
Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Aliquam dignissim tincidunt
turpis. Mauris pede. Vestibulum gravida magna id nibh. In nec urna. Sed ut purus.
Duis sit amet lacus ornare massa mattis consequat. Donec nec tellus. Nam quis nulla
viverra diam faucibus dictum. Nulla facilisi. Donec sit amet dolor at sapien accumsan
consectetuer.
</div>
<div class="calloutDown">
<div class="calloutDown2">
</div>
</div>
<div>
<a href="#">Ramesh Soni</a> Said</div>
</div>

User:Kernst/common.css

2012-06-28T16:55:47Z

Kernst: Created page with ".calloutUp { height: 0; width: 0; border-bottom: 12px solid #ffffff; border-left: 12px dotted transparent; border-right: 12px dotted transparent; left: 0p..."

.calloutUp
{
height: 0;
width: 0;
border-bottom: 12px solid #ffffff;
border-left: 12px dotted transparent;
border-right: 12px dotted transparent;
left: 0px;
top: 0px;
margin-left: 20px;
z-index: 10;
}
.calloutUp2
{
position: relative;
left: -10px;
top: 2px;
height: 0;
width: 0;
border-bottom: 10px solid #9999ff;
border-left: 10px dotted transparent;
border-right: 10px dotted transparent;
z-index: 11;
}
.calloutDown
{
height: 0;
width: 0;
border-top: 12px solid #ffffff;
border-left: 12px dotted transparent;
border-right: 12px dotted transparent;
left: 0px;
top: 0px;
margin-left: 20px;
z-index: 11;
}
.calloutDown2
{
position: relative;
left: -10px;
top: -12px;
height: 0;
width: 0;
border-top: 10px solid #9999ff;
border-left: 10px dotted transparent;
border-right: 10px dotted transparent;
z-index: 10;
}
.divContainerUp
{
background-color: #9999ff;
border: solid 1px #ffffff;
position: relative;
top: -1px;
z-index: 9;
width: 500px;
padding: 4px;
}
.divContainerDown
{
background-color: #9999ff;
border: solid 1px #ffffff;
position: relative;
top: 1px;
z-index: 3;
width: 500px;
padding: 4px;
}
.divContainerMain
{
background-color: #ccccff;
padding: 8px;
}

User:Kernst/Sandbox

2012-06-28T16:51:50Z

Kernst: Created page with " <div class="divContainerMain"> <h3> Up Side Callout</h3> <div> <a href="#">Ramesh Soni</a> Said</div> <div class="calloutUp"> <div class="cal..."

<div class="divContainerMain">
<h3>
Up Side Callout</h3>
<div>
<a href="#">Ramesh Soni</a> Said</div>
<div class="calloutUp">
<div class="calloutUp2">
</div>
</div>
<div class="divContainerUp">
Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Aliquam dignissim tincidunt
turpis. Mauris pede. Vestibulum gravida magna id nibh. In nec urna. Sed ut purus.
Duis sit amet lacus ornare massa mattis consequat. Donec nec tellus. Nam quis nulla
viverra diam faucibus dictum. Nulla facilisi. Donec sit amet dolor at sapien accumsan
consectetuer.
</div>
 
 
<h3>
Down Side Callout</h3>
<div class="divContainerDown">
Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Aliquam dignissim tincidunt
turpis. Mauris pede. Vestibulum gravida magna id nibh. In nec urna. Sed ut purus.
Duis sit amet lacus ornare massa mattis consequat. Donec nec tellus. Nam quis nulla
viverra diam faucibus dictum. Nulla facilisi. Donec sit amet dolor at sapien accumsan
consectetuer.
</div>
<div class="calloutDown">
<div class="calloutDown2">
</div>
</div>
<div>
<a href="#">Ramesh Soni</a> Said</div>
</div>

Fennec/NativeUI/UserExperience/ReaderMode

2012-06-28T16:37:49Z

Kernst:

Below is the proposed first version of a reader mode for mobile Firefox.
* All the mockups (some old) can found in this [http://www.flickr.com/photos/patrykdesign/sets/72157628389027877/ Flickr folder].
* Bug [http://bugzilla.mozilla.org/show_bug.cgi?id=750678 #750678] is related to reading list navigation (and may end up implementing some of the mockups below).
* Other reader mode bugs are tracked by [https://bugzilla.mozilla.org/show_bug.cgi?id=696921 #696921] and [http://lucasr.org/2012/06/21/reader-mode-in-firefox-mobile/ this blog post] shows screenshots of an early UI implementation from June 2012. 
==User Interaction==
===1. How to Access Reader Mode from the Browser?===
Problem: The new browser design is heading towards a chromeless / buttonless aesthetic, how do we introduce the reader mode? 
Solution: The reader mode can hidden the the menu invoked by pressing the hardware/software menu button or with an icon which appears in the URL bar. In tablets there is another possible interaction: it would be interesting to have a feature (perhaps ON by default) where when you rotate the device from landscape to portrait the page would automatically enter reader mode. 
https://farm8.staticflickr.com/7017/6560941471_5153493ffa_b.jpg 
[http://www.flickr.com/photos/patrykdesign/6560941471/in/set-72157628389027877/ Proposed Visual Design Mock Up]
 

===2. Proposed Interactions===
Problem: Add functionality to the reader mode while still maintaining a chromeless, reading focused layout. 
Solution: Introduce off screen menus rendered visible with swiping gestures. 
https://farm8.staticflickr.com/7008/6517216455_d480da0ea1_b.jpg 
[http://www.flickr.com/photos/patrykdesign/6517216455/in/set-72157628389027877 Sample Interaction Flow] 
https://farm8.staticflickr.com/7166/6560945787_f996192027_b.jpg 
[http://www.flickr.com/photos/patrykdesign/6560945787/in/set-72157628389027877 Proposed Visual Design Mock Up] 
https://farm8.staticflickr.com/7015/6589809399_8a96004c7d_b.jpg 
[http://www.flickr.com/photos/patrykdesign/6589809399/in/photostream Examples of Article Navigation (Potentially for a future release)]
 

===3. The Toolbar===
Problem: How do we access / display the various options without intruding on the reading experience 
Solution: On tapping of the screen a translucent tool bar appears, further options can be invoked by pressing the menu icon in the bar, or the hardware menu key. 
https://farm8.staticflickr.com/7202/6964642207_bdcff2b041_b.jpg 
[http://www.flickr.com/photos/patrykdesign/6964642207/in/photostream Proposed Visual Design Mock Up]
 

===4. Visual Variations===
Various Examples: 
https://farm8.staticflickr.com/7149/6560944301_67bccaaee8_b.jpg 
[http://www.flickr.com/photos/patrykdesign/6560944301/in/photostream/ Overall Layout & Typography, Sans Serifs will likely be Open Sans as seen in the later mock ups] 
https://farm8.staticflickr.com/7147/6560942271_dd0e2d08fe_b.jpg 
[http://www.flickr.com/photos/patrykdesign/6560942271/in/photostream/ Colour Themes] 
https://farm8.staticflickr.com/7145/6560945017_c71c0b0b7b_b.jpg 
[http://www.flickr.com/photos/patrykdesign/6560945017/in/photostream/ Image Treatement, ideally if we could aim for the left example, flush layout.]
 

===5. Scalability===
https://farm8.staticflickr.com/7051/6964643319_6224330a9b_b.jpg 
[http://www.flickr.com/photos/patrykdesign/6560940929/in/photostream/ Typography size scaling ratio pairs, we will need to create different ones for 7" and 10" tablets] 
https://farm8.staticflickr.com/7194/6821932828_7aeda656c3_b.jpg 
[http://www.flickr.com/photos/patrykdesign/6821932828/in/photostream Phone to Tablet scaling, notice titles and picture location is different, we will need custom settings for various form factors] 
https://farm8.staticflickr.com/7195/6964642677_73c976d66f_b.jpg 
10.1" Tablet, looks great in portrait 
https://farm8.staticflickr.com/7180/6964642743_71b50a0794_b.jpg 
A bit awkward in landscape, but ok for v.1 
https://farm8.staticflickr.com/7197/6964642807_a12551d989_b.jpg 
Perhaps we can add images or article scroll menu in landscape to maximize the space? v.1 would be nice, but if not v.2? 

==Discoverability==
Early [https://bugzilla.mozilla.org/show_bug.cgi?id=696921#c6 user feedback] in bug [https://bugzilla.mozilla.org/show_bug.cgi?id=696921 696921] suggests that discoverability may be an issue. Attached are some examples of prior art (mostly iOS apps, with links to source) for "first-launch" help screens. Some first-use help is implemented as a "walkthrough" with several steps, or even a "play-through" as with some of the Tapbots apps. Others have shaded overlays with callouts describing the various UI elements, or make use of a blank "home" screen within the app to highlight elements of the UI.

===First-Launch Help Screens: Prior Art===

====The [http://tapbots.com Tapbots] iOS apps====
These apps have very intuitive first-launch help screens which introduce new users to UI controls and gestures. The Convertbot app even has a "play-through" animated demonstration of the app's features.

[[File:Tweetbot first-launch help.png|thumb|200px|left|First launch help for Tapbot's [http://tapbots.com/software/tweetbot/ Tweetbot] app for iOS, showing swipe gestures.]][[File:Convertbot first-launch help.png|thumb|200px|none|The first launch help for [http://tapbots.com/software/convertbot/ Convertbot] is an animated "play-through."]]
{{clear}}

====[http://instinctivecode.com/favorites/ Favorites 2] by Matt Gemmell====
When the app is first launched, the empty speed dial screen shows this help:

[[File:MattGemmell Favorites2 UI.jpg|thumb|200px|none|First launch help for the [http://instinctivecode.com/favorites/ Favorites] iOS app]]
{{clear}}

====[http://sophiestication.com/articles/ Articles] by Sophia Teutschler====
This is another app with a very minimalist UI, like Fennec. When no articles are open within the app, a callout directs the user to the search bar at the top of the screen.

[[File:Articles first-launch help.png|thumb|200px|none|First-launch help for Sophiestication's [http://sophiestication.com/articles/ Articles] iOS app.]]
{{clear}}

Template:Clear

2012-06-28T16:21:34Z

Kernst: A convenience template swiped from Wikipedia's Template:Clear

<div style="clear:{{{1|both}}};"></div><noinclude>
A simple template to clear floats in the page layout.

This can be used, for example, after a left-floated image (''e.g.'', <code><nowiki>[[File:TheImage.jpg|left]]</nowiki></code>) within a subheading to left-align the next paragraph. Normally, the paragraph following the float would get "stuck" to the right side of the image, and the float would only get "cleared" by a subsequent subheading or a manual clear.

==Usage==
To include this template in a page, use the template syntax:
<pre>
<nowiki>{{clear}}</nowiki>
</pre>
where the clear is desired on the page. No visible output will be rendered on the page in place of the template.

Clearing either margin (defaults to both) is accomplished with a template parameter as follows: 
{|class=wikitable
|width=50%|Clear the '''left''' margin (''i.e.'', move all other block-level elements out of the way along the left side of the container element)||align=center|<code><nowiki>{{clear|left}}</nowiki></code>
|-
|Clear the '''right'''' margin (''i.e.'', move all other block-level elements out of the way along the right side of the container element)||align=center|<code><nowiki>{{clear|right}}</nowiki></code>
|}
</noinclude>

File:Tweetbot first-launch help.png

2012-06-28T15:59:50Z

Kernst: A screenshot of [http://tapbots.com/software/tweetbot/Tapbot Tweetbot]'s first-launch help screen, which walks first-time users through UI controls and gestures.

A screenshot of [http://tapbots.com/software/tweetbot/Tapbot Tweetbot]'s first-launch help screen, which walks first-time users through UI controls and gestures.

File:Convertbot first-launch help.png

2012-06-28T15:55:50Z

Kernst: Tapbot [http://tapbots.com/software/convertbot/ Convertbot]'s first-time user help. On first launch, users are presented with a "play-through" demonstration of all the features of the app's UI.

Tapbot [http://tapbots.com/software/convertbot/ Convertbot]'s first-time user help. On first launch, users are presented with a "play-through" demonstration of all the features of the app's UI.

File:Articles first-launch help.png

2012-06-28T15:53:48Z

Kernst:

Screenshot of [http://sophiestication.com/articles/ Sophiestication Article]'s "new tab" page, illustrating the first-launch help for new users.

File:Articles first-launch help.png

2012-06-28T15:52:28Z

Kernst: Screenshot of [http://sophiestication.com/articles/ Sophiestication Article]'s "new tab" page.

Screenshot of [http://sophiestication.com/articles/ Sophiestication Article]'s "new tab" page.

File:MattGemmell Favorites2 UI.jpg

2012-06-28T15:33:12Z

Kernst: Screenshot of a first-launch help screen, from Matt Gemmell's [http://mattgemmell.com/2011/10/31/favorites-2-ui-design/ personal blog].

Screenshot of a first-launch help screen, from Matt Gemmell's [http://mattgemmell.com/2011/10/31/favorites-2-ui-design/ personal blog].

Fennec/NativeUI/UserExperience/ReaderMode

2012-06-28T14:40:52Z

Kernst: Added links to relevant Bugzilla bugs

Below is the proposed first version of a reader mode for mobile Firefox. All the mockups (some old) can found in this [http://www.flickr.com/photos/patrykdesign/sets/72157628389027877/ Flickr folder]. Bug [http://bugzilla.mozilla.org/show_bug.cgi?id=750678 #750678] is related to reading list navigation (and may end up implementing some of the mockups below). Other reader mode bugs are tracked by [https://bugzilla.mozilla.org/show_bug.cgi?id=696921 #696921] and [http://lucasr.org/2012/06/21/reader-mode-in-firefox-mobile/ this blog post] shows screenshots of an early UI implementation. 
1. How to Access Reader Mode from the Browser? 
Problem: The new browser design is heading towards a chromeless / buttonless aesthetic, how do we introduce the reader mode? 
Solution: The reader mode can hidden the the menu invoked by pressing the hardware/software menu button or with an icon which appears in the URL bar. In tablets there is another possible interaction: it would be interesting to have a feature (perhaps ON by default) where when you rotate the device from landscape to portrait the page would automatically enter reader mode. 
https://farm8.staticflickr.com/7017/6560941471_5153493ffa_b.jpg 
[http://www.flickr.com/photos/patrykdesign/6560941471/in/set-72157628389027877/ Proposed Visual Design Mock Up]
 

2. Proposed Interactions 
Problem: Add functionality to the reader mode while still maintaining a chromeless, reading focused layout. 
Solution: Introduce off screen menus rendered visible with swiping gestures. 
https://farm8.staticflickr.com/7008/6517216455_d480da0ea1_b.jpg 
[http://www.flickr.com/photos/patrykdesign/6517216455/in/set-72157628389027877 Sample Interaction Flow] 
https://farm8.staticflickr.com/7166/6560945787_f996192027_b.jpg 
[http://www.flickr.com/photos/patrykdesign/6560945787/in/set-72157628389027877 Proposed Visual Design Mock Up] 
https://farm8.staticflickr.com/7015/6589809399_8a96004c7d_b.jpg 
[http://www.flickr.com/photos/patrykdesign/6589809399/in/photostream Examples of Article Navigation (Potentially for a future release)]
 

3. The Toolbar 
Problem: How do we access / display the various options without intruding on the reading experience 
Solution: On tapping of the screen a translucent tool bar appears, further options can be invoked by pressing the menu icon in the bar, or the hardware menu key. 
https://farm8.staticflickr.com/7202/6964642207_bdcff2b041_b.jpg 
[http://www.flickr.com/photos/patrykdesign/6964642207/in/photostream Proposed Visual Design Mock Up]
 

4. Visual Variations 
Various Examples: 
https://farm8.staticflickr.com/7149/6560944301_67bccaaee8_b.jpg 
[http://www.flickr.com/photos/patrykdesign/6560944301/in/photostream/ Overall Layout & Typography, Sans Serifs will likely be Open Sans as seen in the later mock ups] 
https://farm8.staticflickr.com/7147/6560942271_dd0e2d08fe_b.jpg 
[http://www.flickr.com/photos/patrykdesign/6560942271/in/photostream/ Colour Themes] 
https://farm8.staticflickr.com/7145/6560945017_c71c0b0b7b_b.jpg 
[http://www.flickr.com/photos/patrykdesign/6560945017/in/photostream/ Image Treatement, ideally if we could aim for the left example, flush layout.]
 

5. Scalability 
https://farm8.staticflickr.com/7051/6964643319_6224330a9b_b.jpg 
[http://www.flickr.com/photos/patrykdesign/6560940929/in/photostream/ Typography size scaling ratio pairs, we will need to create different ones for 7" and 10" tablets] 
https://farm8.staticflickr.com/7194/6821932828_7aeda656c3_b.jpg 
[http://www.flickr.com/photos/patrykdesign/6821932828/in/photostream Phone to Tablet scaling, notice titles and picture location is different, we will need custom settings for various form factors] 
https://farm8.staticflickr.com/7195/6964642677_73c976d66f_b.jpg 
10.1" Tablet, looks great in portrait 
https://farm8.staticflickr.com/7180/6964642743_71b50a0794_b.jpg 
A bit awkward in landscape, but ok for v.1 
https://farm8.staticflickr.com/7197/6964642807_a12551d989_b.jpg 
Perhaps we can add images or article scroll menu in landscape to maximize the space? v.1 would be nice, but if not v.2?