commit d109e7a1a639d7a4e25fd7ec1bc5b67abf2e1c29 Author: Mike Perry mikeperry-git@fscked.org Date: Thu Feb 28 13:47:14 2013 -0800

Fix a typo and mention some resolution plans. --- docs/design/design.xml | 14 ++++++++++++-- 1 file changed, 12 insertions(+), 2 deletions(-)

diff --git a/docs/design/design.xml b/docs/design/design.xml index 6609661..bd2b610 100644 --- a/docs/design/design.xml +++ b/docs/design/design.xml @@ -1447,7 +1447,7 @@ a Firefox patch</ulink>. We create two prefs, <command>browser.display.max_font_attempts</command> and <command>browser.display.max_font_count</command> for this purpose. Once these limits are reached, the browser behaves as if -<command>browser.display.use_document_fonts</command> was reached. We are +<command>browser.display.use_document_fonts</command> was set. We are still working to determine optimal values for these prefs.

</para> @@ -1478,7 +1478,7 @@ properties of the content window, but report an effective size of 0 for all border material, and also report that the desktop is only as big as the inner content window. Additionally, new browser windows are sized such that their content windows are one of a few fixed sizes based on the user's -desktop resolution. +desktop resolution.

</para> <para><command>Implementation Status:</command> @@ -1498,6 +1498,16 @@ url="https://gitweb.torproject.org/torbrowser.git/blob/maint-2.4:/src/current-pa a fixed set of system colors to content window CSS</ulink>.

</para> + <para> + +To further reduce resolution-based fingerprinting, we are <ulink +url="https://trac.torproject.org/projects/tor/ticket/7256%22%3Einvestigating +zoom/viewport-based mechanisms</ulink> that might allow us to always report +the same desktop resolution regardless of the actual size of the content +window, and simply scale to make up the difference. However, the complexity +and rendering impact of such a change is not yet known. + + </para> </listitem> <listitem>User Agent and HTTP Headers <para><command>Design Goal:</command>