TorBrowser windows should be only a few possible different initial sizes

A user in #tor suggested that we could provide an option to fix window resolution at 800x600. This isn't a bad idea.

[Automatically added by flyspray2trac: Operating System: All]

added MikePerryIterationFires20110630 actualpoints::2 component::torbrowserbutton owner::koryk points::4 priority::high resolution::fixed status::closed type::enhancement version::1.2.4 labels

PDE has some good data on screen resolutions from panopticlick that we could provide. He's also of the opinion that we should consider not setting window.screen to the current window size and instead a common resolution that is larger than the current window resolution, so we look less like tor users. However, this is debatable, as it can leak some anonymity set based on the chosen resolution.

Trac:
Priority: minor to major
Keywords: N/A deleted, N/A added
Description: A user in #tor suggested that we could provide an option to fix window resolution at 800x600. This isn't a bad idea.

[Automatically added by flyspray2trac: Operating System: All]

to

A user in #tor suggested that we could provide an option to fix window resolution at 800x600. This isn't a bad idea.

[Automatically added by flyspray2trac: Operating System: All]
Milestone: N/A to N/A

Trac:
Owner: N/A to koryk
Parent: N/A to N/A
Status: new to assigned

I definitely support PDE's opinion on the subject.

However, in case the current "round to 50px" feature is retained, can common resolutions be excluded from the rounding? For example, my current resolution is the fairly common 1280x720: with torbutton enabled, it gets reported as a very unusual resolution which actually lowers my anonimity.

This is important because many third-party ad/analytics services don't store the IP address of the user (or the fact that he was browsing from a Tor exit node) but they DO store the screen resolution. Tor users therefore become readily identifiable via their unusual screen resolution, while they could have been easily hidden in the general public.

Considering how widespread services like Google Analytics are, I think this would be an important enhancement for Torbutton.

Trac:
Username: iliketor

Trac:
Actualpoints: N/A to N/A
Points: N/A to N/A
Component: Torbutton to TorBrowserButton

My thinking for this is to make the default resolution in Tor Browser be 800x600, or the largest resolution that will fit inside the user's display. Not sure if this means we should rip out the Firefox code that tries to remember your window resolution, or just handle this entirely in Torbutton though.

Trac:
Keywords: N/A deleted, MikePerryIteration20110612 added
Points: N/A to 4

Trac:
Keywords: MikePerryIteration20110612 deleted, N/A added

Alright, we now have a hidden option that will set the resolution of new windows to a collection of sizes, using the largest one available for a given desktop.

Choosing a spoofed desktop value for window.screen should be a different bug.

Trac:
Status: assigned to closed
Keywords: N/A deleted, MikePerryIterationFires20110630 added
Resolution: None to fixed
Actualpoints: N/A to 2

Retitling to more accurately reflect the implementation,

Trac:
Summary: Provide 800x600 fixed window size option to TorBrowser windows should be only a few possible different initial sizes

closed

changed time estimate to 32h

added 16h of time spent

mentioned in issue #1382 (closed)

mentioned in issue #2907 (closed)