[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #10095 [TorBrowserButton]: Setting screen resolution to a multiple of 200 x 100 is not working reliably with patch in #8478
#10095: Setting screen resolution to a multiple of 200 x 100 is not working
reliably with patch in #8478
----------------------------------+--------------------------------
Reporter: gk | Owner: mikeperry
Type: defect | Status: new
Priority: critical | Milestone:
Component: TorBrowserButton | Version:
Resolution: | Keywords: tbb-fingerprinting
Actual Points: | Parent ID:
Points: |
----------------------------------+--------------------------------
Comment (by cypherpunks):
>> Maybe just close the damned first window immediately and open a new
one?
> The tricky thing is closing the first window before it is visible
Is that really neccessary? If the window is closed after it's visible then
from a user's perspective there'll just be a sort of flicker. Seems okay
until a better solution comes along?
(I know next to nothing about JS and Firefox extensions, so my own attempt
ended up with an endless loop of windows opening and closing.)
>> And could someone ask upstream if there's some kind of "all extensions
have initialized" notification?
> And your notification does not help as the window is shown *before* all
extensions are initialized/the chrome is overlaid.
Isn't that good as well? Window opens with a wrong size for a fraction of
a second, we get the notification and do the resize, and it's stable
because all extensions have been initialized.
The only case not completely fixed would be starting TB with an URL
argument.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/10095#comment:10>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs