The Browser Toolbox shows that this window has the min-width: 700px; and min-height: 500px; properties, so you can't go below those dimensions.

That is my complaint! That it is now FORBIDDING me from sizing it as-needed, which I have been doing pretty much since forever!

This paternalistic pointless misfeature is not even documented as one of the total number of changes, rendering it a stealth misfeature. I can understand not documenting a genuinely trivial change, but this is NOT at all trivial!

In the real world, it is axiomatic that, "If it works, don't fix it."

I nominate as the Official Slogan of Firefox, "If it works, fix it!"

I found my shortcut for the FTP site, and downloaded 106.0 -- hoping I do not get into a pitched battle with some other misfeature trying to block my efforts. If I succeed, I guess that will probably be the end of the line for updates for me, meaning I'll then need to find some way of turning off the "update available" nagbox (frankly, finding such a convenience feature would shock me).

Meanwhile, although I downloaded the Win64 version, does anyone know what the other two versions (shown in the screencap below) have as a raison d'etre?

Will either of them work with existing add-ons? More importantly, will either of them NOT have the BROKEN Library box behavior?

Well, so much for that adventure.

While at this point I'm more than willing to take the gamble, it appears that someone forgot to include the "Proceed Anyway" button.

I know there's some way of skipping past THIS annoybox (having read about it at some point) -- does anyone know the trick?

"Firefox Setup 106.0" --allow-downgrade does NOT work, argh....

Now off to see if they've "merely" CHANGED that handy option, or thrown it entirely off a cliff.

You can use CSS code in userChrome.css to adjust those two properties and make them smaller.

• /questions/1397089 Library Panel's Increasing Minimum Size Has Become a Workflow Interuption Issue

Add CSS code to the userChrome.css file in the chrome folder in the Firefox profile folder.

window#places {
 min-width: 100px !important;
 min-width: 300px !important;
}

It is not that difficult to create userChrome.css if you have never used it.

The first step is to open the "Help -> Troubleshooting Information" page and find the button to access the profile folder with the random name (xxxxxxxx.default-release).

• https://support.mozilla.org/en-US/kb/use-troubleshooting-information-page-fix-firefox

You can find the button to go to the profile folder under the "Application Basics" section as "Profile Folder -> Open Folder". If you click this button then you open the profile folder in the Windows File Explorer. You need to create a folder with the name chrome in the profile folder with the random name (name is all lowercase). In the chrome folder you need to create a plain text file with the name userChrome.css (name is case sensitive). In this userChrome.css text file you paste the text posted. On Mac you can use the TextEdit utility to create the userChrome.css file as a plain text file.

In Windows saving the file is usually the only time things get more complicated because Windows can silently add a .txt file extension and you end up with a file named userChrome.css.txt. To avoid this you need to make sure to select "All files" in the dialog to save the file in the text editor using "Save File as".

You need to close (Quit/Exit) and restart Firefox when you create or modify the userChrome.css file.

More info about userContent.css and userChrome.css in case you are not familiar: *https://www.userchrome.org/what-is-userchrome-css.html

• https://www.userchrome.org/how-create-userchrome-css.html
• https://www.userchrome.org/firefox-changes-userchrome-css.html

In Firefox 69 and later you need to set this pref to true on the about:config page to enable userChrome.css and userContent.css in the chrome folder.

• about:config => toolkit.legacyUserProfileCustomizations.stylesheets = true
• https://support.mozilla.org/en-US/kb/about-config-editor-firefox

Mea culpa, I attempted the switch at installation time rather than run time of installed program. Once again, common sense gets in the way, effect potentiated by multiple concussions resulting from repeated application of "If it works, fix it" rule.

So, here I am, back in 106land, with my USABLE download box returned. Bookmarks and History unmolested, meaning I won't have to figure out some way of restoring my profile.

In order to back it up, I had to copy the tree into a .7z file, due to the numerous complaints of too-long path/file names. OK, that worked -- but what if I need to RESTORE it??? I assume that Windows will again whine about too-long filenames (which, due to its bifurcated path/file length limits -- one for its own use, with a shorter one imposed on the shell -- leaves us in a situation in which the OS is perfectly happy to CREATE and MAINTAIN "too long" filenames, but break like a rotten egg if the user tries to COPY them.

Now, off to see if I'll be able to use my existing shortcuts for FF, or, if I'll need to edit them to include the "--allow-downgrade" switch each time I start FF.

Oh, great... I forgot about all those times that FF will be started when I doubleclick on a shortcut! If it's going to insist on behaving that way, I guess I can look forward to some exciting Registry editing fun.

All this happytime because some nimrod said, "Hey, I can add a line of code and break the Library box so that it won't be able to get smaller than I like it to be!"

>You can use CSS code in userChrome.css to adjust those two properties and make them smaller.

[...]

Thanks, I'll try that, hopefully it'll do the trick. (I'd wondered if there was a .css somewhere that defined this abomination.)

This whole event is a real sad commentary on the current state of mozillathink.