User manual

This line is meant to stop the browser from trying to load the Favicon after loading

the website. Usually, a website has another special icon that differs it from other

websites and clearly identifies the website in a browser bar with several tabs. For

the browser to load this character, it will send a second request query after calling

the page and ask for this Favicon. You may have noticed this additional Request

query in your first experiments with the TCP server. To prevent the second query

and keeps unnecessary stress from the board, the above code line informs the

browser not to send a second Request. I recommend using this line for your own

HTML pages.

The second special feature in this document is the Color-Picker element that I

mentioned. It replaces the buttons in the previous example. This is a relatively new

HTML5 element.

In the previous website, we simply used buttons of the type submit so that the form

values were transmitted directly when pushing them. This is, unfortunately, not

possible when using an input element of the type color. One way of solving this

problem would be creating a button of type submit that would have to be pushed

separately after setting the colour. We will demonstrate this in a later experiment.

Here, we have entered a small JavaScript code (this is the part on-

change="this.form.submit()"), which transfers the form immediately after a change.

The Color-Picker element in the Android-5.0-

browser

This way, we do not need an extra button.

001

002

003

</form>