This will add a tooltip for each of the marks, indicating to the user
the missing information in the database. The color orange is used when
some fields are not populated.

If the value is set to "{}", the information shall be considered null.
This situation can append when removing an information from the detail
page, a null object is send to the server and stored in the database.

This behaviour should also be patched on the backend part.

This may be related to the issues seen by users to configure the
account. This bug is only confirmed on Firefox on Mac.

The configuration error is a 500 due to a missing 'password' field in
the session, probably related to a clear of the session.

This clear of session only being done on the opening of the /config
page, it could be that Firefox reload the page or re-do a query in the
background, hence clearing the session.

This bug is not reproducible on Chromium nor Firefox on Linux.

Move all the files in the "templates/submission" folder.

Rename the "submission" folder to "user". This folder only contains html
templates files related to the "submission" users.

Remove useless variable assignation and user r"" for special logger
string.

This page was useless, and slowing too much the interface and the
server. If we want to open an image for a donor in particular, open
first the donor page, then we can all the information we want for this
donor.

This change will offload the generation of the list of all application
related .js and .css files to python (based upon the content of the
'app' directory), and pass the full list, html formatted, to the jinja
renderer.

The 'enter' key on the username field should focus on the password
field, and not send the current form to validation.