Opened 5 years ago

Closed 5 years ago

#11078 closed defect (worksforme)

TBB Doesn't Respond to Programmatic Maximize Request

Reported by: cypherpunks Owned by: mikeperry
Priority: Medium Milestone:
Component: TorBrowserButton Version:
Severity: Keywords: tbb-usability
Cc: CRhode@… Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

I use TBB on Gnome3 (Debian Wheezy). Past versions of TBB would respond to programmatic screen maximize requests from a *devilspie* daemon that recognized windows titles (or application names) as soon as they appeared. Many applications such as *emacs* and *gnome-terminal* still do. The version of Firefox included in the current TBB does not. I understand this is an anti-fingerprinting "feature" that has been introduced recently.

The TBB default window size does not fit entirely on my screen. In particular the URL Status line is off the bottom of the screen. It is impractical for me to run TBB with the default window dimensions. I imagine it is for many other users, too. This attempt to enforce a default window configuration needs to be relaxed; you can take anti-fingerprinting only so far.

I am able to F11 to full-screen, but this requires intervention and deprives me of the shell status bar.

I am able to maximize TBB manually. Apparently it will accept a programmatic maximization request from the shell. I just need it to respond to an automatic request from a running daemon, as well.

Thanks for your attention. -ccr-

Child Tickets

Change History (7)

comment:1 in reply to:  description ; Changed 5 years ago by gk

Component: Tor bundles/installationTorBrowserButton
Keywords: tbb-usability added; TBB devilspie maximize removed
Owner: changed from erinn to mikeperry

Replying to cypherpunks:

I use TBB on Gnome3 (Debian Wheezy). Past versions of TBB would respond to programmatic screen maximize requests from a *devilspie* daemon that recognized windows titles (or application names) as soon as they appeared. Many applications such as *emacs* and *gnome-terminal* still do. The version of Firefox included in the current TBB does not. I understand this is an anti-fingerprinting "feature" that has been introduced recently.

Yes, see: #9738 where we had one user *complaining* that the browser auto-maximized.

The TBB default window size does not fit entirely on my screen. In particular the URL Status line is off the bottom of the screen.

Not sure what you mean but that might be a different bug. Could you file one and attach a screenshot showing the problem?

I am able to maximize TBB manually. Apparently it will accept a programmatic maximization request from the shell. I just need it to respond to an automatic request from a running daemon, as well.

That should be possible generally. Torbutton is only observing (and acting on) maximize events during start-up. Later on all sorts of maximizing is working (be it done automatically or manually) to allow users customizing their browser as they please.

comment:2 in reply to:  1 ; Changed 5 years ago by gk

Replying to gk:

during start-up. Later on all sorts of maximizing is working (be it done automatically or manually) to allow users customizing their browser as they please.

"Later on" means here something like "< 1 sec after the browser window got visible".

comment:3 Changed 5 years ago by CRhode

Cc: CRhode@… added

comment:4 in reply to:  1 Changed 5 years ago by CRhode

Replying to gk:

The TBB default window size does not fit entirely on my screen. In particular the URL Status line is off the bottom of the screen.


Not sure what you mean but that might be a different bug. Could you file one and attach a screenshot showing the problem?


Sure. Here is Bug #11319: TBB Automatically Chooses an Inappropriate Size for Its Main Window

comment:5 in reply to:  2 Changed 5 years ago by CRhode

Replying to gk:

"Later on" means here something like "< 1 sec after the browser window got visible".

Yes, I can use *devilspie* to (re)maximize TBB after 1.0 sec. Shorter waits don't work.

I can specify a pause in the s-expressions used in the devilspie config files. This is documented in lots of examples available here and there from around the Web.

There is a follow-on *devilspie2* that uses *lua* scripts in place of s-expressions. It is much less robustly documented, and fewer how-to's exist for it. I don't know how to specify pauses in *lua*.

comment:6 Changed 5 years ago by CRhode

... so TBB does respond to programmatic maximize requests -- just not in real time. My bad!

I'm willing to close this Bug as "Not a Problem!"

comment:7 Changed 5 years ago by gk

Resolution: worksforme
Status: newclosed

Thanks for helping debugging this.

Note: See TracTickets for help on using tickets.