[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #32308 [Applications/Tor Browser]: Stop inner letterbox jiggling as border is dragged
#32308: Stop inner letterbox jiggling as border is dragged
-------------------------------------------------+-------------------------
Reporter: cypherpunks | Owner: tbb-
| team
Type: defect | Status: new
Priority: Medium | Milestone:
Component: Applications/Tor Browser | Version:
Severity: Normal | Resolution:
Keywords: tbb-9.0-issues, tbb-fingerprinting- | Actual Points:
resolution |
Parent ID: | Points:
Reviewer: | Sponsor:
-------------------------------------------------+-------------------------
Comment (by tom):
This may be at odds with what letterboxing is aiming for. It sounds like
OP is looking for the (gray) border size to stay constant while the window
is resized and when the resizing stops, the content window snaps and gets
resized to the correct size.
The opposite is actually the ideal solution: as you resize, the gray
border will smoothly increase and decrease and the content window will
move as it is recentered in the window. This would cause very noticeable
jumps in content window size as the browser passes a threshold for the
letterboxing.
This is the ideal because we only want to report a letterboxed dimension
to web content, never an in-between value.
This is very similar to
https://bugzilla.mozilla.org/show_bug.cgi?id=1556014 although 1556014 is a
little different because the problem is that as you resize, the website
can read some intermediate values. (As I explain there though, I'm not
concerned about that.)
Now because I'm not really concerned about those intermediate values,
letting the content grow (without growing the grey border) as I explain in
the first paragraph is not the worst thing (even though it does go against
the goal of letterboxing.)
I suppose, in a perfect world, we could figure out something where we
improve this situation in a way that looks smooth but doesn't reveal
intermediate values.
Today; however, I do not know how to accomplish any of these goals. We are
not handling 'beginresize' and 'endresize' events, we are recalculating
things based on a single 'resize' event that occurs and I don't know how
to infer a resize that's begin and not completed.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/32308#comment:2>
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