Signed-off-by: Luiza Wille <lmwc14@inf.ufpr.br>

The RGB order was backwards compared to the pixel format we've
requested, resulting in the red and blue channels getting swapped.

Avoid applying this workaround more than necessary. Also comment a
bit more why this hack is needed.

It needs to update whenever the viewport or clipping changes, so
let's make sure that actually happens and not trigger on mildly
related events.

The scaling is relative the current viewport, so we need to make
sure it is correct before changing the scale setting.

Don't overwrite the user's configured choice. Instead ignore
settings when they cannot be respected.

IE apparently doesn't support removing several class specifiers at
once, so switch to several calls.

The previous problems were because we were scrolling the wrong element,
so we can enable this feature now.

Other parts of the code shouldn't have to care about this. Let Display
convert between canvas coordinates and framebuffer coordinates.

It's not used in modern event handlers.

It's an old propriatary IE thing that isn't necessary.

It mostly dealt with scrolling which we don't use. It also made mistakes
in some cases. Remove it and compute the coordinates directly in the
calling code.

Adds comments that clarifies why they are needed. Also narrows the
handler for contextmenu a bit.

Fix some corner cases.

Fixes issue #773

PhantomJS has a very basic implementation of Uint8Array, so we
need to help it out a bit.

If no authentication is required then we should pick the None
option to avoid bothering the user.

Chrome sucks at calculating the size and gets confused due to the
scrollbars. Hide the scroll bars while resizing.

The browser tells us which element was under the cursor, so we don't
have to calculate it ourselves.

This makes sure we get consistent behaviour across all browsers.

Try to keep the virtual keyboard up even more. Only release focus
when it is absolutely necessary.

We use the more specific function now, even though it is usually an
alias.

Change the look of the "busy" spinner a bit. It's mostly used for
connection stuff, so give it a more data flow feel. Also bling it
up a bit with some fading. Perty sells. :)

We require standard adherence now, so remove tests that assume
the old system.

We no longer limit writes to the socket.

The native WebSocket is in a much better position to do queue
management than us. We also failed to check the return value and
set up a timer, causing stalls.

This gets us in sync with websockify as of 40238b00.

The element we want scrolling around is noVNC_screen, not the entire
window. This also allows us to compute the screen size without
fiddling the scrollbars on and off.

It causes the browser to redo the layout needlessly otherwise,
having annoying effects like moving the scroll position.

Put it so it matches where it is in the HTML.

The previous attempt could leave parts of the canvas outside the
document, making it impossible to reach. Use a safer method as
recommended by Mozilla.

Save settings immediately

There is no reason to why this shouldn't be possible.

Adds a new section for all functions that add event handlers.

Moves the one handler for the status out of the function as well. It
didn't fit in with the function's old name either.

Retire the old settingsApply. This also allows UI logic to check the
state of things using the settings instead of having to look at the
values of HTML elements (we couldn't be sure if the changes were
applied yet or not).