commit 045097194dece98b3c8df732531b0f303cf2ab72 Author: Mike Perry mikeperry-git@fscked.org Date: Mon Apr 4 17:10:24 2011 -0700
Clear out old Firefox bugs.
Also fix a couple typos found by arma. --- website/design/design.xml | 21 ++++++++++++++------- 1 files changed, 14 insertions(+), 7 deletions(-)
diff --git a/website/design/design.xml b/website/design/design.xml index c589de8..4997cfa 100644 --- a/website/design/design.xml +++ b/website/design/design.xml @@ -577,10 +577,10 @@ years past. <title><ulink url="https://gitweb.torproject.org/torbutton.git/blob_plain/HEAD:/src/components/torRefSpoofer.js">@torproject.org/torRefSpoofer;1</ulink></title> <para> -This component handles optional referrer spoofing for Torbuton. It implements a +This component handles optional referer spoofing for Torbutton. It implements a form of "smart" referer spoofing using <ulink url="https://developer.mozilla.org/en/Setting_HTTP_request_headers">http-on-modify-request</ulink> -to modify the Referrer header. The code sends the default browser referrer +to modify the Referer header. The code sends the default browser referer header only if the destination domain is a suffix of the source, or if the source is a suffix of the destination. Otherwise, it sends no referer. This strange suffix logic is used as a heuristic: some rare sites on the web block @@ -2043,7 +2043,7 @@ sent. The default value is 1. The smart referer spoofing is implemented by the </para> <para> This setting also does not directly satisfy any Torbutton requirement, but -some may desire to mask their referrer for general privacy concerns. +some may desire to mask their referer for general privacy concerns. </para> </sect3>
@@ -2188,7 +2188,7 @@ bug interferes with Torbutton's ability to satisfy its <link linkend="setpreservation">Anonymity Set Preservation</link> requirement. </para> </listitem> - +<!-- <listitem><ulink url="https://bugzilla.mozilla.org/show_bug.cgi?id=280661">Bug 280661 - SOCKS proxy server connection timeout hard-coded</ulink> @@ -2202,6 +2202,7 @@ of privacy and security issues of its own (in addition to being unmaintained).
</para> </listitem> +--> <listitem><ulink url="https://bugzilla.mozilla.org/show_bug.cgi?id=418986">Bug 418986 - window.screen provides a large amount of identifiable information</ulink> @@ -2284,7 +2285,7 @@ linkend="setpreservation">Anonymity Set Preservation</link> requirement. </para> </listitem> <listitem><ulink -url="https://bugzilla.mozilla.org/show_bug.cgi?id=122752%22%3ESOCKS +url="https://bugzilla.mozilla.org/show_bug.cgi?id=122752%22%3EBug 122752 - SOCKS Username/Password Support</ulink> <para> We need <ulink url="https://developer.mozilla.org/en/nsIProxyInfo">Firefox @@ -2334,6 +2335,7 @@ requirement on Firefox 3. </listitem> </orderedlist> </sect2> +<!-- XXX: Need to create a bug for DOM storage APIs at some point --> <sect2 id="FirefoxWishlist"> <title>Bugs blocking functionality</title> <para> @@ -2342,7 +2344,7 @@ The following bugs impact Torbutton and similar extensions' functionality.
<orderedlist>
- +<!-- <listitem><ulink url="https://bugzilla.mozilla.org/show_bug.cgi?id=445696">Bug 445696 - Extensions cannot determine if Firefox is full screen</ulink> @@ -2355,8 +2357,9 @@ to resize maximized and minimized windows when it should not.
</para> </listitem> +--> <listitem><ulink -url="https://bugzilla.mozilla.org/show_bug.cgi?id=629820%22%3EnsIContentPolicy::s... not +url="https://bugzilla.mozilla.org/show_bug.cgi?id=629820%22%3EBug 629820 - nsIContentPolicy::shouldLoad not called for web request in Firefox Mobile</ulink> <para>
@@ -2371,6 +2374,7 @@ which will also cause more problems for porting Torbutton.
</para> </listitem> +<!-- <listitem><ulink url="https://bugzilla.mozilla.org/show_bug.cgi?id=290456">Bug 290456 - Block/clear Flash MX "cookies" as well</ulink> @@ -2386,6 +2390,7 @@ it would be nice if there was a standard way to do this from a Firefox API.
</para> </listitem> +--> <listitem><ulink url="https://bugzilla.mozilla.org/show_bug.cgi?id=417869">Bug 417869 - Browser context is difficult to obtain from many XPCOM callbacks</ulink> @@ -2476,6 +2481,7 @@ workarounds. </para>
<orderedlist> +<!-- <listitem><ulink url="https://bugzilla.mozilla.org/show_bug.cgi?id=435151">Bug 435151 - XPCSafeJSObjectWrapper breaks evalInSandbox</ulink> <para> @@ -2490,6 +2496,7 @@ properly though.
</para> </listitem> +--> <listitem><ulink url="https://bugzilla.mozilla.org/show_bug.cgi?id=440892">Bug 440892 - network.protocol-handler.warn-external are ignored</ulink>