Hello!
tjr asked during our last meeting whether we would consider testing Letterboxing[1] in Tor Browser even if it still were on ESR60. Here are a bunch of questions he had and we can think about in this thread:
Q: If it was ready in a 60-based Alpha would you ship it then or would you want to wait until 68?
I think we could easily test it in 9.x alphas being still on ESR60. This might in fact be a good idea as we got quite some pushback last time when we tried to fix #14429 (which, admittedly, has been a couple if years ago). One thing to worry about is how complicated the backport would be. If not really that problematic, then bonus points for that plan from my side at least.
Q: What is the minimal viable product user experience wise? Q: Does the margin needed different color or watermark?
I don't think so.
Q: Do you need a button to disable it globally or after an individual resize?
I'd be fine with a preference being exposed.
Q: Do you need it to work on mobile?
No.
Q: For very low resolution - under 100 pixels in a dimension - does it need to do something intelligent or just not do any margins at all?
I am not sure I understand the question, could you elaborate?
Q: Does it need a user walkthrough explainer? (Probably I think... maybe you can start thinking of how that would look?)
I think that sounds like a good idea. It could be another example for the general task of how to introduce new features (tracked in #29768). One idea could be that we want to have different strategies depending on how invasive a feature is: there might be features that are okay getting introduced with our onboarding and others that might need a different treatment. There are probably cons to this idea, though, like we would start training users to look at different places for getting to know whether there are new features or not. But on the other hand, we probably don't want to put everything into the onboarding either...
Georg