Tell us the values of all your privacy.resistFingerprinting.letterboxing.* preferences?
Check whether this happen also on a fresh Tor Browser install (clean profile)?
Set the privacy.resistFingerprinting.jsmloglevel to Info (capitalized this way) and report your Browser Console (ctrl+shift+J) output filtered by RFHelper.jsm?
I am willing to share a diff of about:config ("Show only modified preferences") between Debian/working and Arch/broken.
But not publicly, since it might contain sensitive information. @ma1 Want me to send you an email?
FWIW I've tried a clean install of Tor Browser 13.0.16 on Ubuntu, disabling letterboxing, then upgrading to 13.5 and I couldn't reproduce yet.
Trying to install and test an Arch VM , but I hope those logs might shed some light in the meanwhile:
Set the privacy.resistFingerprinting.jsmloglevel [about:config preference] to Info (capitalized this way) and report your Browser Console (ctrl+shift+J) output filtered by RFHelper.jsm?
No, it goes away! But immediately when letting my window manager resize TBB to the full screen estate, it's back.
OK, we're onto something.
Letterboxing, even if disabled, is used to round the inner sizes of new windows to integers, in order to prevent subpixel fingerprinting.
This mechanism assumes that initial windows are forced to a fixed, pre-defined size (which wouldn't show any letterboxing border), but it seems tiled window manager break this assumption.
So ATM this behavior is saving your windows from being (more) fingerprintable, but the price is that letterboxing is not hidden as it would meant to be in your setup.
Not sure what would be the best course of action here, between:
Accept the sizes forced by the tiled layout, making users fingerprintable
Keep things as they are (i.e. "hidden letterboxing" become visible and save the day), making users puzzled
Do 1 but warn users as we do for maximized windows
Personally, I chose screen real estate over fingerprinting-protection, so I want to disable letterboxing completely. (And I think that TBB saying "Letterboxing is currently disabled." should do exactly that. :)
ma1changed title from Letterboxing remains enabled after flipping relevant prefs to Letterboxin visible even if disable with tiled window managers
changed title from Letterboxing remains enabled after flipping relevant prefs to Letterboxin visible even if disable with tiled window managers
ma1changed title from Letterboxin visible even if disable with tiled window managers to Letterboxing visible even if disable with tiled window managers
changed title from Letterboxin visible even if disable with tiled window managers to Letterboxing visible even if disable with tiled window managers
Just want to share a simple workaround I found: open a new window that is initially tiled at a different size than you ultimately want. It seems like this issue is only triggered when you resize to the exact pixel size that the window was when it first opened - it happens even if you resize to the exact size manually.
So for me I just start the browser, ctrl+N to open another window which tiles alongside the original (making both windows half the desired final size), then close the original window, which gives the new window the full desired size and no letterboxing. You can even move existing letterboxed tabs from the old window to the new one and they will be fixed.
I understand resources like developer time are limited. And I apologize for not being able to provide a patch.
But I do want to stress that I encounter this bug multiple times every single day. It is annoying, counter-intuitive and - adding up - also time-consuming. This is the first time in many years of daily TBB use that disabling a default-enabled feature doesn't work (as expected).
I am unable to find a scheduled release date for 14.5. But I for one would really appreciate to have a fix within a few months- over (almost) a year.
Let me know if there is anything - apart from coding - I can help with.
@ilf 14.5 is scheduled for Spring 2025, though depending on when in the release cycle a fix is developed, it may be backported to the 14.0 series before then.