Re: [tor-bugs] #32324 [Applications/Tor Browser]: Introduce Letterboxing to users

["Tor Bug Tracker & Wiki" <blackhole@xxxxxxxxxxxxxx>]

#32324: Introduce Letterboxing to users
-------------------------------------------------+-------------------------
 Reporter:  antonela                             |          Owner:  tbb-
                                                 |  team
     Type:  defect                               |         Status:  new
 Priority:  Medium                               |      Milestone:
Component:  Applications/Tor Browser             |        Version:
 Severity:  Normal                               |     Resolution:
 Keywords:  ux-team, tbb-9.0-issues,             |  Actual Points:
  TorBrowserTeam201912                           |
Parent ID:                                       |         Points:
 Reviewer:                                       |        Sponsor:
-------------------------------------------------+-------------------------

Comment (by Thorin):

 Just throwing an idea out there which could cover a few items, including
 this one.

 If you look at
 https://ghacksuserjs.github.io/TorZillaPrint/TorZillaPrint.html, I added
 notation to the inner window measurement (which updates in real time)
 which provides red or green `[LB]` and `[RFP New Window]` notation
 - i.e if the window is at 200's width and 100`s height capped at 1000,
 then RFP New Window is green, and same for LB based on the 50, 100, 200
 pixel stepping. Note: if zoom is not 100%, I change to an orange notation.

 What if we use a toolbar button. I realize we don't want to waste real
 estate (we're capped at 1000px wide) and we already have the slider and
 new identity (but we did take away the No Script and HTTPS-Everywhere
 icons, by default).

 The button could present three states: for lack of better words red,
 amber, grey/neutral
 - [a] red: new window is out, LB is off (just check the pref)
 - [b] amber: new window is out, LB is on
 - [c] neutral: new window is good (LB doesn't apply since LB's steps fit
 new windows)

 When clicking the button, it's panel would always provide a learn more
 link. And based on the state below, it could provide extra info
 - in [a] we can recommend that letterboxing be used and link to the
 letterboxing UI
 - in [b] we could provide an action to resize to the a default new window
 (see #16364)

 In onboarding we could can point at the button

 Three possible issues, not insurmountable
 - 1. Users who opt in to turn off letterboxing via the UI (when it lands)
 might also want to "never remind me about this again" i.e not be
 "annoyed/distracted" by the situation in [a]
 - 2. handling zooming, which is per tab. Switching between a zoomed and
 non-zoomed tabs would need to be taken into account. I assume core code
 can easily still get the non-zoomed measurements
 - 3. in a default TB, it would be grey (unless resized) and not actually
 highlight LBing to new users or new installs. We can do that in onboarding
 (but that wouldn't be there forever), so we can also track if the button
 has ever be clicked, and when in mode [c], if never clicked then apply
 something like an overlay of a bouncing green dot.

 This could not only be used to highlight/introduce LBing, but also educate
 users not to deviate from new window sizes (depending on their threat
 model in the learn more link), and be used for dual purposes such as
 #16364.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/32324#comment:15>
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