How to set Chrome download popup window size? <SOLVED>

[dcung]

Anyone knows how to set Chrome download popup (default) window size?
On monitors/laptops that have lower res, I can't see the bottom part, and have to resize the popup each time to use it.

2024-11-05-065509_1920x1080_scrot.png (92.32 KiB) Viewed 1040 times

[pp4mnklinux]

Hi, @dcung ;

I'm sorry, I had the same problem and unfortunately, Chrome doesn't provide a built-in way to set the default size of the download popup window, but you can try some tricks:

The easier is use a Chrome Extension so u are not going to see this screen again (I don't like it a lot, but it is an option). There is another solution, I can't explain it because it's a question of "good luck".

You must resize this popup and close it.- As I told u, I don't know why, but after resizing it to your preferred size when you close it sometimes, Chrome remembers the last size used, so reopening might maintain the new size. (to close it don't use the cross icon at the top right corner, but right click at the top and close -memory).

These solutions are workarounds since there isn't a direct setting in Chrome to adjust the popup size.

It is possible someone can explain it better and solve your problem ,but, meanwhile , you can try this.

Have a nice day.

[mikewalsh]

@dcung :-

As @pp4mnklinux says, there's no direct way to alter the popup window size. Another possibility is to move the window around, in order to be able to reach the bits you need.....

Linux has long had the ability to move a window without needing to access the title bar. To do this, place the cursor anywhere you like within the window itself. Click and hold the 'Alt' key, then click - and hold - the left mouse button. The cursor changes to a '4-way arrow'.....and NOW you can drag the window in any direction you want.

Let us know if that functionality helps you at all.

Mike.

[dcung]

Linux has long had the ability to move a window without needing to access the title bar.

I know this.

The point is that I prefer not to have default window size that is bigger than screen resolution.

[MochiMoppel]

Anyone knows how to set Chrome download popup (default) window size?

I don't know Chrome. I'm using Bookworm64 and sometimes Chromium where I have set the window size of these "popup" windows via a JWM Group option.

You can check if Chrome, like Chromium, assigns a dedicated window name:

• Open the "Location" window (as in your screenshot)
• Open a terminal window and run the command xprop WM_CLASS
• Mouse cursor will turn into cross
• Click on the "Location" window

The terminal output in my case would be
WM_CLASS(STRING) = "xdg-desktop-portal-gtk", "Xdg-desktop-portal-gtk

This means that in file /root/.jwm/jwmrc-personal I can add Group options for all windows with the name "xdg-desktop-portal-gtk". This name is used by Chromium for Open/Save dialogs and maybe other windows (haven't checked)
<Group>
<Name>xdg-desktop-portal-gtk</Name>
<Option>width:600</Option>
<Option>height:450</Option>
<Option>centered</Option>
</Group>

After running the obligatory jwm -restart command all File Open/Save dialogs in Chromium are opened with a size 600x450.
May also work in Chrome.

[dancytron]

Another non-answer, but in MX Linux there is a setting to put the buttons at the top of the screen instead of at the bottom, so they aren't cut off.

It applies everywhere, not just Chrome.

[fredx181]

@dcung

On monitors/laptops that have lower res, I can't see the bottom part, and have to resize the popup each time to use it

.
Same thing here, tested with LXQT build (not sure if it's different with another DE perhaps).

I may have to do with running as user from root login (user puppy in this case), found a little trick:
- login as puppy, resize the popup window, try again and the size is remembered from what I tested.
- login as root again, run chrome and the popup window size should be as you adjusted earlier.
Inconvenient workaround though, but can't figure out what's a real solution.

[HerrBert]

I may be wrong, but the screenshot in the first post looks like the gtk3 filechooser.

In s15pup64, i can change the window size for min browser running as spot using gsettings:
run-as-spot gsettings set org.gtk.Settings.FileChooser window-size '(824, 622)'

[MochiMoppel]

In s15pup64, i can change the window size for min browser running as spot using gsettings:
run-as-spot gsettings set org.gtk.Settings.FileChooser window-size '(824, 622)'

Nice
Works here too and affects all applications that use the GTK3 FileChooser. I'm running as root, thus
gsettings set org.gtk.Settings.FileChooser window-size '(824, 622)'

[dcung]

Same thing here, tested with LXQT build (not sure if it's different with another DE perhaps).

I may have to do with running as user from root login (user puppy in this case), found a little trick:
- login as puppy, resize the popup window, try again and the size is remembered from what I tested.
- login as root again, run chrome and the popup window size should be as you adjusted earlier.
Inconvenient workaround though, but can't figure out what's a real solution.

This has been bugging me for a while, just not enough to post about it. Been looking for answer in background on net, but none that suitable for me yet.
My daily laptop is 1920x1080 - so a non-issue here, but as a tinkerer I do laptop/pc hopping often, and when I do, I get reminded about this annoying issue from time to time.

I already noticed that it happened on multiple DE (at least LXQT, DDOG builds that I am positive).
I don't use login manager, but I understand the gist of your suggestion.
I have tested your suggested little trick, and found it working.
Initially tested with LXQT, and since I know it also happened/annoyed me in DDOG, I tested on that too, and it works there too (DDOG build).

Now, while doing that, I also found/realized that - puppy user in LXQT and DDOG has different defaults (ie. notice different sizes).
I thought/expected they are the same, since root user has same default. But the little trick works nonetheless - which is good.
This reminded me articles/postings that I encountered during my background research that I didn't/don't understand. Which in short, related to what @MochiMoppel & @HerrBert suggested. If I can understand what they are saying, maybe later I can incorporate this into my mod-mklive and have 'the solution' built-in OOTB.
I do 'crash & burn' frugal install too frequently - OOTB solution is nice to have.

But meanwhile, your trick is the closest solution to what I am after. Thanks Fred!

Now I will try to digest @MochiMoppel & @HerrBert suggestions.
Thanks to all suggestions.

[fredx181]

I may be wrong, but the screenshot in the first post looks like the gtk3 filechooser.

In s15pup64, i can change the window size for min browser running as spot using gsettings:
run-as-spot gsettings set org.gtk.Settings.FileChooser window-size '(824, 622)'

Thanks !

@dcung
So probably for DebianDog this will do (using equivalent (run-as-user) of run-as-spot):
run-as-user gsettings set org.gtk.Settings.FileChooser window-size '(824, 622)'

[dcung]

So probably for DebianDog this will do (using equivalent (run-as-user) of run-as-spot):
run-as-user gsettings set org.gtk.Settings.FileChooser window-size '(824, 622)'

I already tried it. I thought if works, I can put it in startup.
(Note - I autologin as root - in all my builds).

In DDOG, got error.

Code: Select all

root@live:~# gsettings set org.gtk.Settings.FileChooser window-size '(824, 622)'
bash: gsettings: command not found
root@live:~# 

In LXQT, no error. Tried both as root and using run-as-user.
But no difference in file-chooser windows size. I tried varying the sizes.
run-as-user gsettings set org.gtk.Settings.FileChooser window-size '(600, 480)'

[fredx181]

@dcung
Indeed with gsettings it doesn't seem to work, but found this post https://forum.xfce.org/viewtopic.php?pid=55276#p55276 , followed the instructions and works for me (on LXQT, I tested)
- install dconf-cli apt install dconf-cli
- extract attached archive etc_dconf.tar.gz in / (so you get new added files in /etc/dconf/)
(modify window-size=(500, 500) in /etc/dconf/db/local.d/00-filechooser as you'd like)
- run dconf update

etc_dconf.tar.gz

extract in /

(403 Bytes) Downloaded 14 times

[dcung]

@dcung
Indeed with gsettings it doesn't seem to work, but found this post https://forum.xfce.org/viewtopic.php?pid=55276#p55276 , followed the instructions and works for me (on LXQT, I tested)
- install dconf-cli apt install dconf-cli
- extract attached archive etc_dconf.tar.gz in / (so you get new added files in /etc/dconf/)
(modify window-size=(500, 500) in /etc/dconf/db/local.d/00-filechooser as you'd like)
- run dconf update
etc_dconf.tar.gz

I tried it both LXQT-Full and LXQT-mini.
Check additional files mentioned existed. Run dconf update. With or without reboot same - not working.
Both not working for me. But my build is not using online conf. I use gvfs instead of pup-volume-monitor.
I'll do more test and report of findings.

Edit 1:
Just tested with DDOG.
Works - I varied windows sizes, run dconf update, works, even without reboot/re-login (root).

No idea yet, why (my) Lxqt not working. These are refresh builds done 2 days ago...both use gvfs.

Edit 2:
Works in OBDOG.
No reboot/relogin needed. Just run dconf update

[dcung]

I make fresh build of Lxgt_Full with online conf, only took out slim.
<do dconf stuff as before, extract etc_dconf.tar.gz, dconf update>
Does not work.

I make fresh build Lxqt (minimal), unmodified online conf, using unmodified mklive.
Then

Code: Select all

apt update
apt install google-chrome-stable run-as-user dconf-cli
extract etc_dconf.tar.gz <as per instruction before>
dconf update

Does not work.

I did this on Fujitsu laptop.
But I tested my Lxqt builds (even from earlier refresh set) on 3 laptops - samsung, fujitsu, Dell D630
None of Lxqt DE works for me.

DDOG, OBDOG DE works.

[fredx181]

I make fresh build of Lxgt_Full with online conf, only took out slim.
<do dconf stuff as before, extract etc_dconf.tar.gz, dconf update>
Does not work.

I make fresh build Lxqt (minimal), unmodified online conf, using unmodified mklive.
Then

Code: Select all

apt update
apt install google-chrome-stable run-as-user dconf-cli
extract etc_dconf.tar.gz <as per instruction before>
dconf update

Does not work.

I did this on Fujitsu laptop.
But I tested my Lxqt builds (even from earlier refresh set) on 3 laptops - samsung, fujitsu, Dell D630
None of Lxqt DE works for me.

DDOG, OBDOG DE works.

Well, sorry, I tested now with a clean LXQT install and doesn't work for me either.
Tried to find out why it worked earlier for me (not on a clean install). but couldn't . Frustrating !

[dcung]

Well, sorry, I tested now with a clean LXQT install and doesn't work for me either.
Tried to find out why it worked earlier for me (not on a clean install). but couldn't . Frustrating !

@fredx181 Thanks for doing that.
I have been pulling my hair making builds using unmod mklive variations of Lxqt with online conf (NMU, Non-NMU, mini, full, with and without slim, etc).
All does not work. I persisted since you could, and I couldn't get it to work - and I 'gotta' know why..
But with your confirmation, at least I know it happens to not only me...

Anyway, I am happy that at least for those low res screen, I now know to put DDOG, OBDOG to avoid this windows size issue.
Glad that you found the 'dconf channel locking' trick nonetheless.

Thanks Fred!

[dcung]

@fredx181

I observed these during testing.

In those that works (DDOG, OBDOG), these non-text files exist OOTB, i.e. clean, fresh build, first login.
/root/.config/dconf/user
/home/puppy/.config/dconf/user
Deleting these files affect the filechooser windows size, i.e. no longer follow what is set in 00-filechooser
I didn't check timestamp, but assume that it gets updated whenever dconf update run

These, don't exist in Lxqt (mklive - OOTB).
After installing dconf-cli, etc, I tried copying these files from DDOG/OBDOG, it gets ignored.

I don't know what the significance, but thought to report what I noticed, in case you can see any connection/relevance.

[fredx181]

@dcung

I observed these during testing.

In those that works (DDOG, OBDOG), these non-text files exist OOTB, i.e. clean, fresh build, first login.
/root/.config/dconf/user
/home/puppy/.config/dconf/user

Yes, good find
What I did just now on LXQT and worked is the following:
- On a clean install, login as puppy and run google-chrome, adjust the popup window size.
- Now that the /home/puppy/.config/dconf/user is created, save that dconf folder to someplace.
- Reboot without save, so again on a clean install, copy the saved dconf folder to /home/puppy/.config/ and make it owned by puppy:
chown -R puppy:puppy /home/puppy/.config/dconf
And from login as root the popup window size should be as you adjusted earlier, nothing else needed from what I tested.

[dcung]

These, don't exist in Lxqt (mklive - OOTB).
After installing dconf-cli, etc, I tried copying these files from DDOG/OBDOG, it gets ignored.

I didn't say it clearly. What I meant it gets ignored, it gets ignored by dconf update

I 'm trying to understand it, since gtk filechooser size appear to effect more than Chrome (in my case).
It effects grsync, firefox, etc. And they seem to have 'default' from everywhere.
So, this dconf channel locking that you found seems a good way to control it 'centrally' - (for me).
It just so happen (wherever grsync, firefox, etc got them from) have defaults less than 768 in height, so it didn't bother me (as much as Chrome).
.
.
.

Yes, good find
What I did just now on LXQT and worked is the following:
- On a clean install, login as puppy and run google-chrome, adjust the popup window size.
- Now that the /home/puppy/.config/dconf/user is created, save that dconf folder to someplace.
- Reboot without save, so again on a clean install, copy the saved dconf folder to /home/puppy/.config/ and make it owned by puppy:
chown -R puppy:puppy /home/puppy/.config/dconf
And from login as root the popup window size should be as you adjusted earlier, nothing else needed from what I tested.

Yes. In fact, I found that we can copy (adjusted) dconf/user from DDOG, OBDOG, etc, and the 'adjustment' retained - provided the permission are correct (accordingly).
I didn't use the login as puppy way, as I don't use login manager - it involves more step (reboots) in my case to do that.
I used root - chrome - no sandbox way, to create the dconf/user file.
But the gist is the same, i.e. to have one's preferred/adjusted dconf/user in /home/puppy/.config/dconf/user.

So, I will mark this post <RESOLVED> as far as Chrome popup windows size.
But, as far as gtk filechooser (dconf-cli), I have no idea why it doesn't work in LXQT.
.
.
.
Another feedback that I want to provide.
Unlike DDOG, OBDOG config, zz_lxqt_config.squashfs doesn't have
/root/.config/dconf/user
/home/puppy/.config/dconf/user

I checked with dconf-editor, the one in DDOG, OBDOG. Filechooser window size (-1, -1).

2024-11-09-063704_609x284_scrot.png (20.34 KiB) Viewed 601 times

I don't know if you want to include those in LXQT too.
From what I observed, with the existence of the files, Chrome (well filechooser really) popup to max height resolution - in lo-res screen (just like in DDOG, OBDOG).
Without it, Chrome popup to over max height resolution (wherever it got it from).
To me, max height is less annoying than over max height.
But I don't know what other settings are in that file.

I'll leave that discretion to you as DebianDog boss...

For myself, I will create a common dconf/user file that I will incorporate in my mod-mklive build.

Thanks @fredx181

[fredx181]

@dcung

I thought to simplify things (you seem to make it more complicated than it is IMO ), by just adding dconf/user to home/puppy/.config in dog-boot-bookworm-20221013 https://debiandog.github.io/MakeLive/do ... 013.tar.gz
(the dconf/user that was created when I logged in as puppy, it contains apparently the geometry setting of the popup window that I adjusted to much smaller)

Tested now making a new (basic) LXQT build with added run-as-user and google-chrome-stable and it works ok (geometry of the popup window is around 700x500)
edit: don't know, btw, how it goes with other build than LXQT (perhaps it still needs the new files in /etc/dconf).

[dcung]

... (you seem to make it more complicated than it is IMO ), by just adding dconf/user to home/puppy/.config in dog-boot-bookworm-20221013 https://debiandog.github.io/MakeLive/do ... 013.tar.gz

I didn't intend to make it more complicated.
When I say I will create a common dconf/user (for DDOG/OBDOG/LXQT - indeed DebianDog in general) in my mod-mklive, it is 'effectively' dog-boot-bookworm-20221013 (?).

I suggested zz_lxqt_config.squashfs only since I observed that you have it zz_ddog_config.squashfs, zz_obdog_config.squashfs.

And I don't know the order of precedence dog-boot-bookworm-20221013 and those zz_config_files - my guess zz takes precedence.
Having it in dog-boot-bookworm-20221013 is fine for LXQT (a better place IMO), but (currently) for DDOG, OBDOG it may get overwritten.
Again - this is a question, not a suggestion. You would know better which takes more precedence.

You would know the flowchart of mklive by heart, I would have to trace it (which I haven't put effort). So, I do mine 'quick and dirty' way for my own use - since I don't know the precedence, and having those file in multiple may overwrite one another. If dog-boot-bookworm-20221013 if the 'version' of dconf/user then good - otherwise...well...

Anyway - I'll stop complicating things....

[fredx181]

Having it in dog-boot-bookworm-20221013 is fine for LXQT (a better place IMO), but (currently) for DDOG, OBDOG it may get overwritten

Yes, you are right, more complicated than I thought (I too much focused on LXQT only), I'll think about it , should perhaps add the dconf/user mod in all the zz modules.

[fredx181]

@dcung
Although it looks like you have your ways (for the filechooser with a fixed (small) size), I went for a different, more general approach:
In fact the source of the problem is a shortcoming of the run-as-user setup/script that the adjusted size of the filechooser is not preserved.

So I focused on fixing that and got it working ok, please test with new run-as-user-package v0.0.8.
apt update; apt install run-as-user

In case /home/puppy/.config/dconf/user is missing, it will be created (at the point of adjusting the filechooser window) and size will be preserved.
If it's existing, then the filechooser will open with the settings from that, but if adjusted, it will be preserved too.

[Luluc]

For whatever it's worth, I handle that kind of problem a bit differently on Openbox (usually LXDE, but may work with LXQT):

Run this:

Code: Select all

$ obxprop | grep OB_APP

The mouse cursor changes so I can click some window with it, which gives me this information for example:

Code: Select all

$ obxprop | grep OB_APP
_OB_APP_TYPE(UTF8_STRING) = "normal"
_OB_APP_TITLE(UTF8_STRING) = "Mozilla Firefox"
_OB_APP_GROUP_CLASS(UTF8_STRING) = "Firefox"
_OB_APP_GROUP_NAME(UTF8_STRING) = "firefox"
_OB_APP_CLASS(UTF8_STRING) = "firefox"
_OB_APP_NAME(UTF8_STRING) = "Navigator"
_OB_APP_ROLE(UTF8_STRING) = "browser"

Then I open ~/.config/openbox/lxde-rc.xml

Your Openbox may have lxde-rc.xml symlinked to rc.xml. Seems to be a popular choice among maintainers.

Then look for the <applications> section and add this:

Code: Select all

<application class="Firefox" name="Navigator" title="Mozilla Firefox">
  <maximized>yes</maximized>
  <focus>yes</focus>
  <fullscreen>no</fullscreen>
</application>

After many years of that, I've grown accustomed to having certain windows always maximized or fullscreen or etc. It really bothers me to use a machine that doesn't have my customizatons (e.g. a fresh install).

You can also force the position and size:

Code: Select all

<position force="yes">
  <x>center</x>
  <y>-908</y>
</position>

<position force="yes">
  <x>600</x>
  <y>-200</y>
</position>

<size>
  <height>600</height>
  <width>1024</width>
</size>

It's a bit of work, but it's worth it in the long run. I've had my customizations for many years. It's shocking to deall with an installation that doesn't have them. Like browsing without ad blockers.