[tor-bugs] #14429 [Tor Browser]: Automated rounding of content window dimensions
Tor Bug Tracker & Wiki
blackhole at torproject.org
Sun Mar 29 20:11:25 UTC 2015
#14429: Automated rounding of content window dimensions
-------------------------+-------------------------------------------------
Reporter: | Owner: arthuredelstein
arthuredelstein | Status: needs_revision
Type: defect | Milestone:
Priority: normal | Version:
Component: Tor | Keywords: tbb-fingerprinting-resolution, tbb-
Browser | torbutton, tbb-4.5-alpha,
Resolution: | TorBrowserTeam201503R, GeorgKoppen201503R
Actual Points: | Parent ID:
Points: |
-------------------------+-------------------------------------------------
Comment (by gk):
Replying to [comment:48 gk]:
> Replying to [comment:47 arthuredelstein]:
> > There is no way for the browser to know about this discrepancy. We can
easily fix the discrepancy with a single call to rebuild, *unless* the
user is still holding the mouse down. So we need to keep calling rebuild
periodically, until we can be sure the user is no longer holding on to the
drag event. The only way to be sure of this is if a mouseover is detected.
So we keep calling rebuild every 250 ms until a mouseover happens.
>
> But what if I use the browser mainly via keyboard (as I often do e.g.)
or if someone is just loading a page and leaving the computer for quite a
while? This behavior made my log grow quite quickly. I wonder even if
scripts could detect this additional continuing load under certain
circumstances given high precision JS timers. How expensive is this
operation?
Just to give some data: I can easily see that updateDimensions() is called
50 times a second. Oh, and moving the mouse on the window does not always
stop that problem . Not sure in which cases this happens, though.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/14429#comment:50>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
More information about the tor-bugs
mailing list