User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:126.96.36.199) Gecko/20060728 Firefox/188.8.131.52 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:184.108.40.206) Gecko/20060728 Firefox/220.127.116.11 Getting, installing, uninstalling and updating are covered. There is nothing on how to find the darn things after you've installed them. It would help to know where they're likely to show up, about using "customize" to install toolbar buttons, etc. There is nothing along these lines in the FAQ, and usually not much at the "homepage" for the extension either. Reproducible: Always I have already documented the use of extensions at my website. [http://cybercoyote.org/software/extensions.shtml#secret]
Summary: No content in built-in help documentation on how to actually use extensions. → Built-in help documentation on extensions is incomplete.
Severity: normal → enhancement
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Windows XP → All
Hardware: PC → All
Summary: Built-in help documentation on extensions is incomplete. → document where extensions "are likely to show up" in the UI
Moving to sumo.
Component: Help Documentation → Knowledge Base Articles
Product: Firefox → Sumo
QA Contact: help.documentation → kb-articles
I'm leaning toward WONTFIXing this one. It's getting into Add-ons user-support territory; and it's incredibly vague.
Virtually all extensions are unique, so explaining how you customize them are not very straightforward. People who install an extension should look for documentation on how to use it at the place they installed the extension from. That said, we could add a section in http://support.mozilla.com/en-US/kb/Customizing+your+Firefox+with+add-ons about the fact that you can (usually) right-click an extension in the list and select Options to change settings.
this seems fixed to me.
myles7897 is right. The "Extension optionspreferences" section of <http://support.mozilla.com/en-US/kb/Customizing+your+Firefox+with+add-ons> has always been there.
Status: NEW → RESOLVED
Last Resolved: 11 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.