This is very annoying. This is a basic and important feature. I move camera with mouse controls. Press Undo. Nothing happens.
Why it is not fixed?

The stubbornness of developers in this matter still amazes me.

In T60695#858934, @Bastien Montagne (mont29) wrote:

@pan beep (beep) this is not a forum to have random chat, but a design task over an highly technical topic. Please refrain from useless comments.

Why this is Normal priority? Undo in Blender 2.8 takes two times more than in 2.7 and is so slow compared to undo in any other application. Starting from simple Notepad to complex ones like Cinema 4d. This should be set the highest priority above all others issues.

This script below does what I want. Maybe it will help other users too.

So what about a simple setting to set the preferences window a fixed size defined by a user? Why can't it be bigger? I guess no one uses 800x600 pixels display anymore.

In T71935#818306, @Julian Eisel (Severin) wrote:

Storing such information would mean we'd have to ensure it works in all kinds of cases - when opened with different monitor setups, different DPIs, different OSes, etc. Versioning may also become problematic: If we change the layout of the window contents, we may have to add extra versioning code to make sure old sizes/positions are updated correctly.
And yes, storing such things may also cause some issues in practice, as @Maciej Jutrzenka (Kramon) mentioned. We don't have an option to restore the default layout yet (although I'd love to have this).
Note that I'm not totally against this - it's just that this would need quite some effort to work reliably, and we have other priorities.
Also related: D4339.

In some cases it's just better to have something simple and predictable, rather than something that tries to be smart and just causes different problems.

Either way, everything works as designed here. If you disagree about the design, that's fine but not something we can deal with on our bug tracker. We have to keep some strict policies here unfortunately.
So thanks for the report, but I don't see a bug here.

In T71935#818261, @Maciej Jutrzenka (Kramon) wrote:

it shouldn't it would cause huge problems where accidentialy you would move it out of the scope.. and usually to fix such issiue u just restart blender etc... Floating windows allways should go to defult position after restart of app

The File Browser remembers the size. It does not remember the position.

In T69652#773544, @Julian Eisel (Severin) wrote:

Any design feedback not strictly about the points mentioned here should go to the design task, T62971. Here we only list the TODOs for 2.81, and maybe try to find solutions to the mentioned open topics.

The new File Browser window is one step forward and few backwards:

• it is great it opens as separate window – this took so long to implement. Finally it is here. Thank you for that!
• the window does not remember previous opened size. People have large displays and want to use that space. Tiny windows like this and like preferences is not a welcome usability fix.
• there is missing Up arrow with two dots .. over files list that allowed to quickly go back. Using only the arrow up that is farther away is a bad idea. Since it was feasible before why it is not now?
• opening a folder using single click was a great Blender's feature. Now it's removed. Why?
• monochromatic, same colour icons makes a list one mess. Why can you introduce colours for folders, blend and image files? It would help so much to distinguish what is what at first look.

Can you change the current undo system to remove the limitation?
This is very irritating when undoing operations while interactive rendering is enabled. The whole scene is being reloaded thus making interactive rendering much less interactive.

THanks for fixing apply modifiers. The shading bug still remains and is causing weird patterns when shadow is enabled. Screen is from my three js project.

Increasing the system cursor size a bit in Accessibility > Display options (OSX System preferences) resolves the issue on High Sierra.

I can confirm it is working now as expected. Thank you for the fix!

I can confirm this issue too on OSX Sierra 10.12.6 The nodes frome example below render as a blank picture:
https://blenderartists.org/t/volumetric-cloud-with-eevee/1138752/3

Thanks for the fix! Now the rendering is ok.

Yes, drivers are up to date.
OctaneRender and Cycles from 2.79b work fine. This issue is with latest experimental 2.79 and 2.8 builds.

Same bug here on High Sierra 10.12.6.