Closed Thorin-Oakenpants closed 2 years ago
Collect the set
who needs fucking peacocks when you can have a nutterbutter
Thank you
also, we passed 4000 stars, so that'll be another beer 🍺 ... we'll catch that @bagder 's curl repo yet
That's over thirteen (I need to learn math) fourteen Spartas + Gerard Buttler
@Thorin-Oakenpants do you like to include this in the README.md?
I feel like the enable session restore
recipe should include user_pref("network.cookie.lifetimePolicy", 0);
at least as an optional for users that still manage cookies with CAD.
My reason for using CAD is that it supports containers. I can allow cookies to be kept for just one permanent container instead of allowing all permanent containers to keep that site's cookies when using the native site exceptions. If I'm wrong on how that works, please correct me.
enable session restore recipe:
places.history.enabled=false
browser.sessionstore.privacy_level=2
(note that I don't use network.cookie.lifetimePolicy=2
).browser.sessionstore.privacy_level=0
restores formdata even with privacy.clearOnShutdown.formdata=true
.user_pref("privacy.window.maxInnerWidth", 1600); user_pref("privacy.window.maxInnerHeight", 900);
Firefox is now higher than with the default of 1000 LOL.
Firefox is now higher than with the default of 1000 LOL
Well, actually, the height is lower. But the width being higher is the whole point.
For me new windows a now higher than before. Anyway my WM maximizes firefox now automatical ly because it is close to maximum, but if you un-maximized it, you see it.
ok ... not sure if I can replicate. I need some numbers. What is your available screen res and system scaling. What is your inner vs outer, just un-maximize, toggle RFP and use TZP) - that is I need to know what the chrome is using)
So you open at A x B, WM maximizes FF, you click restore, but it doesn't restore to A x B?
Also, I know there are "bugs" with new win, including tiling managers (even at 1000 x 1000 max) - and IDK if anything can be done about external programs altering new win after the fact - and that is what letterboxing fixes. On the bright side, you're opening maximized and therefore getting as much real estate as possible on smaller screens (under 1600x900) - which was the plan
Seems to be some mess between Firefox/RFP and the WM.
🔸 maxInner: 1600x900 RFP: on
🔸 flip RFP of and reload
1920 x 1080
available (for all intents and purposes: i.e it does not matter if you are twice as large but at 200% system scaling)117 x 190
which is not right: LB is still on
12 x 126
xulstore.json
in yur profile remembers last window positions and sizes) - we can ignore this as a symptom and not a problem IMO10'ish x 120'ish
1800'ish x 950'ish
for inner to work with, and 1600 x 900 fits in there - as per your previous test🔸 maxInner: 1000x1000 RFP: on
1800'ish x 950'ish
for inner to work with, and 1000 x 900 fits in there🔸 maxInner: 1600x900 RFP: on letterboxing: false
So it's your tiling manager kicking in, but you still conform to the max sizes, get more real-estate, and letterboxing protects you. The restore bit is a bit confusing for me. Is it maximizing or resizing to fit the screen - because the 1090 height is weird. Anyway, it's all a bit moot when it's an external program
You can change the max values if you want if you don't like being "maximized", or can you tell the tiling manager to ignore firefox? IDK - up to you
Actually it's a compositing WM.
changelog: v94
FF94 release notes FF94 for developers FF94 security advisories
CHANGELOG: [all changes]
:star: your friendly reminder to run prefsCleaner
9999
6050
new in user.js v94
made inactive in user.js v94
STATS