-
|
I've had the following minor issue for over a week, and at first I was reasonably sure that it was a Brave problem. But, after experiencing the same issue on Firefox and having multiple scroll updates and one or two Brave updates since, I'm finally breaking down to ask (it's really not a big deal, just a nuisance...). When I download a file in Brave, I get the file picker pop-up dialogue. For a long stretch, it popped up centered, at whatever size I had previously resized to, and the "Save" button was defaulted so that if I simply hit Enter, the file saved to the default directory. For the past week+, the very first time I save a file, the save dialogue opens full screen (yes, I know that you know that I like actual windows to open full screen). After that, until I reboot, it will open at whatever size I set it to on that first open (which is why this is only a minor nuisance). However, no matter what, the Save button is no longer defaulted. I have to click it with the mouse explicitly. I assume (but haven't tried) that I can tab over and press Enter, but the original default behavior has changed. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 6 replies
-
|
I don't use Brave, but Firefox stores the latest size of windows, and when re-opened, they open with the stored size. I don't know anything about default buttons, but it has nothing to do with the compositor, it is an application "feature". Maybe you can control the behavior with one of their billion configuration options :-) |
Beta Was this translation helpful? Give feedback.
The compositor controls the size of windows after they are created, but initially respects the size requested by the application when they are floating. That is where Firefox sends the stored value from eaerlier. Dialogs are usually created for a specific purpose, and then destroyed. scroll will only store the size of a floating window if you decide to make it tiled, and then will restore the previous floating size if you make it float again.
About buttons, the compositor knows nothing about them. They are just elements controlled by the application (the UI toolkit), which renders them onto the window buffer, and controls focus etc. For scroll, in general, the whole window is just a buffe…