H2S55: Basic HTML.syntax-lib:

H3S1: Tags:

H4S1: <p>:

Hu: In addition to declaring a paragraph, the <p> tag also comes with an automatic | <br> # W3Schools<a-r>: Default.CSS-settings<where.was-this??><fbno>: Most browsers will display the <p> element with the following default values:

p {
  display: block;
  margin-top: 1em;
  margin-bottom: 1em;
  margin-left: 0;
  margin-right: 0;
}

Hu: The above W3Schools inclusion indicates that # there is already CSS in HTML, and therefore, it’s better to speak of editing | CSS, rather than adding it.

H4S2: <a>:

W3Schools: The most important attribute of the <a> element is the href | attribute, which indicates the link’s destination.

H4S4: <div>:

W3Schools: The tag defines a division or a section in an HTML document. The tag is used as a container for HTML elements – which is then styled with CSS or manipulated with JavaScript. The tag is easily styled by using the class or id attribute. Any sort of content can be put inside the tag! Note: By default, browsers always place a line break before and after | the element. Hu: Each tag type corresponds with an element, and HTML uses these terms pseudo-interchangeably. The main | application of <div>, which has no function in-itself, is to demarcate, in code, a division, upon which some styling can be segmentally–applied<Turing>

H4S5: <textarea>:

W3: The tag defines a multi-line text input control. Hu: Default input fields in HTML do not come with automatic line breaks, when users reach the right border of the form input box, but <textarea>, which can be used in substitution to a <input> tag in a form, and can be assigned name, and id attributes, to be posted to PHP-processing, does.

H3S2: Attributes:

Hu: Attributes must be separated from the tag name by at least a space:

Wrong code<fbno>: <phidden...>

Hu: The hidden attribute will not affect the tag.

H4S1: Class attribute:

W3: The class attribute can be used on any HTML element. Hu: The class attribute is an example of a connector | object whose sole purpose of existence, within a prog–lang, is to enable a connection, with another prog-lang, and its behavior. Specifically, the class | attribute increases the adaptability of HTML, which is an element–specific language, with CSS, which is a class–specific | language, logically, by allowing you to assign elements to classes, in HTML, a subset to set | relationship<ch-2><Turing> W3: It can also be used by a JavaScript to access and manipulate elements with the specific class | name.

.city {
  background-color: tomato;
  color: white;
  border: 2px solid black;
  margin: 20px;
  padding: 20px;
}

<div class="city">
<div class="city">

Hu: The “.” convention is added ahead of user.created-classes, as opposed to elemental classes, such as <table>, which are predefined, and connected, already, in base.HTML/CSS<Turing!>

H4S2: Event attributes<gestures!><Turing>:

Hu: HTML has more default event | attributes, and more can be custom built, based on their combination<Turing>, than even iOS-applications, which means it’s erroneous, and fallacious, to associate iOS, with gestures, simply because HTML can also be used by applications without touch-screens. Event.attributes-lit,rev:

H5S1: //

H4S3: type=”hidden”:

W3Schools: The <input type="hidden"> defines a hidden input field. A hidden field lets web developers include data that cannot be seen or modified by users when a form is submitted. A hidden field often stores what database record that needs to be updated when the form is submitted. Note: While the value is not displayed to the user in the page’s content, it is visible (and can be edited) using any browser’s developer tools or “View Source” functionality. Do not use hidden inputs as a form of security!

H4S4: Global attributes<a-r>:

H3S3: HTML controls browser.security-lockdowns:

Hu: HTML can be considered synonymous, to an extent, to web-browsers, and there’s a significant entanglement, in particular, in security-practice, due to this inter-dependency. Historically, according to Wang, Lengstorf, Leggetter et al, browsers have erred on the side of caution, such that when there has been # a sufficient proliferation of hacking behavior within one pocket of functionality, as it pertains to a particular web-API<WP.MIC-H2S66>, the reaction has been to shut down support, for that API, or feat-component, entirely. It’s significant that HTML-5, in coordination with the top.5-browsers, have this kind of leverage, in dictating the user’s web-experience, and this must be accounted for, because we will be designing on top of the browsing-stack<WP-MIC-H2S67>. Note that web-browsers are an independent security component<fbno> to firewalls, and IPs, both in your internal control, such as your modem, and the telecoms’ control, so what may be permitted, by every other juncture, may be disallowed by the browser, and that would, alone, prevent you from accessing that feature. Therefore, navigating this aspect of the browser’s security-component is a necessary step to the design of any web-app, or feat, that depends upon the browser’s functionality, as an access-portal<Turings>

H4S1: Cross-Document Messaging:

<Wang pg-3>: C.D-M overcomes the same-origin limitation by allowing messages to be exchanged between different origins. When you send a message, the sender specifies the receiver’s origin and when you receive a message the sender’s origin is included as part of the message. The origin of the message is provided by the browser and cannot be spoofed. On the receiver’s side, you can decide which messages to process and which to ignore. You can also keep a “white list” and process only messages from
documents with trusted origins.

H3S4: HTML.browser-compilation,lit.rev:

<WP.MIC-H2S119><WP.MIC-H2S88>Hu: HTML is compiled in and by the user‘s web–browser, which is a desktop | application, after the file, in bulk |=syn,here<fbno> blob has been delivered to the user‘s side<Turing>; the output of the HTML-compiler is pixels on the screen, which means that what is displayed, to the user, to his visual | neurons, the next step of computing thereafter, with its own compilers, and so forth<ch-42>, is not the only thing that is loaded, into the user’s computer, but if the user has inference<ch-8>, then that which is in his computer<Biblical>will also enter his brain, through another pathway, which is why the loaded but not displayed needs to be programmed responsibly.