Opened 8 months ago

Last modified 6 months ago

#31821 new defect

reapply window.open() clamping

Reported by: Thorin Owned by: tbb-team
Priority: High Milestone:
Component: Applications/Tor Browser Version:
Severity: Normal Keywords: tbb-fingerprinting-resolution, ff68-esr
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

In alpha we seem to have lost the 10px clamping for new windows (which are opened in a new tab: see #9881 )

Pic to follow: example of a user resizing the browser for more real estate: which we want to encourage for uptake and for the letterboxing buckets to be less FP'able (I assume).

Would be good to upstream it

Child Tickets

Attachments (2)

LB-bypass.png (23.1 KB) - added by Thorin 8 months ago.
previous-behavior.png (11.9 KB) - added by Thorin 8 months ago.
10px clamping

Download all attachments as: .zip

Change History (5)

Changed 8 months ago by Thorin

Attachment: LB-bypass.png added

Changed 8 months ago by Thorin

Attachment: previous-behavior.png added

10px clamping

comment:1 Changed 8 months ago by gk

Keywords: ff68-esr added
Priority: Very HighHigh

I am not sure whether we want to *encourage* resizing. However, we are good with the defaults, right? I agree, though that this is an important bug to get fixed.

comment:2 Changed 8 months ago by Thorin

However, we are good with the defaults, right?

Sure. I meant that currently LB is not tied to RFP (i.e. separate pref) and there is https://bugzilla.mozilla.org/show_bug.cgi?id=1538130 which suggests removing new window sizing completely. FYI: I think we should keep it (if that's what you mean by "defaults", and also fix it with the toolbar visible where it throws height out by several pixels), but a consensus hasn't been reached.

comment:3 Changed 6 months ago by Thorin

Just a heads up, I can bypass the old clamping method (I'll email the details), so when/if we do this, we'll have to think of a more robust solution

Note: See TracTickets for help on using tickets.