As you type, needs to save flips on/off with each letter typed, e.g. true (keydown) false (keydown) true (keydown) false etc.

Describe the bug
When an alert pops up, it is not shown in the middle, it is shown off center.

To Reproduce
Steps to reproduce the behavior:

1. Type alert(1) in the console
2. See issue

Expected behavior
The alert is shown in the middle

Information

• OS: MacOS
• Browser: All
• Version: 1.0.0

Additional context
This feature broke when window placement was switched from em to vh.

Currently there is only the calculator, though all other than the file viewer and app store should be added.

This happens if the user restarts, and so is a pretty major issue. I think the fix is to add a login button to the welcome screen if the user is a google user.

Here is an example of this being done with fetch which is already what we are using:
https://fetch-progress.anthum.com/fetch-basic/
This is an enhancement that I feel would help people understand how long the page is going to take to load, rather than them just hoping it will be done soon.

It could be either a percentage or a bar, I feel a percent might be better for the layout of the loading screen right now though.

Should be pretty simple to fix, just check if onSignIn has been called already.

When you have multiple large files the filesystem doesn't update.
The server gives a 413 error. It looks like the max size can be increased, but we'll have to look in to that

This happens when you open a blank document and press command + s

I think I've found the cause of many memory leaks in the system. The issue is that a lot of apps add listeners to the window object, and those listeners don't go away when the element is removed from the document. Since those listeners are arrow functions, they close over the entire class and thus nothing can get garbage-collected.

Here's one example:
https://github.com/UltimatePro-Grammer/websystem/blob/4d5138172f8370cebb70faf54652f24aba3d86e4/js/appstore.js#L231-L236

This only happens when signed in with google.

This is not intended behavior, just like the app's name isn't I feel the tags shouldn't be either.

This behavior may actually be what we want; Though it seems like we should delete it in the database after some amount of days to save space on the server.

It is always the default blue.

Should be as simple as just checking if the user has data on the server before running setup.js