Explore topic-wise InterviewSolutions in Current Affairs.

This is not POSSIBLE USING only HTML.

This is not possible using only HTML.

<EMBED src="media/background.mpeg" loop="INFINITE" autostart="TRUE">

<embed src="media/background.mpeg" loop="infinite" autostart="true">

&LT;META http-equiv="PRAGMA" VALUE="NO-CACHE"&GT;

<meta http-equiv="PRAGMA" value="NO-CACHE">

Each ELEMENT and attribute declaration in this specification is ACCOMPANIED by its document type definition fragment. We have chosen to include the DTD fragments in the specification rather than seek a more approachable, but longer and less precise means of DESCRIBING an element’s properties. The following tutorial should allow readers unfamiliar with SGML to read the DTD and understand the TECHNICAL details of the HTML specification.
•DTD Comments
•Parameter entity definitions
•Element declarations
•Attribute declarations

Each element and attribute declaration in this specification is accompanied by its document type definition fragment. We have chosen to include the DTD fragments in the specification rather than seek a more approachable, but longer and less precise means of describing an element’s properties. The following tutorial should allow readers unfamiliar with SGML to read the DTD and understand the technical details of the HTML specification.
•DTD Comments
•Parameter entity definitions
•Element declarations
•Attribute declarations

SGML is a system for DEFINING markup languages. Authors mark up their documents by representing structural, presentational, and semantic information ALONGSIDE CONTENT. HTML is one EXAMPLE of a markup language.

SGML is a system for defining markup languages. Authors mark up their documents by representing structural, presentational, and semantic information alongside content. HTML is one example of a markup language.

following general principles when working with HTML 4.0.

Separate structure and presentation
HTML has its roots in SGML which has always been a language for the specification of structural markup. As HTML matures, more and more of its PRESENTATIONAL elements and attributes are being replaced by other mechanisms, in particular style SHEETS. Experience has shown that separating the structure of a document from its presentational aspects reduces the cost of SERVING a WIDE range of platforms, media, etc., and facilitates document revisions.

Consider universal accessibility to the Web
To make the Web more accessible to everyone, notably those with disabilities, authors should consider how their documents may be rendered on a variety of platforms: speech-based browsers, braille-readers, etc. We do not recommend that authors limit their creativity, only that they consider alternate renderings in their design. HTML offers a number of mechanisms to this end (e.g., the alt attribute, the accesskey attribute, etc.)

Furthermore, authors should keep in mind that their documents may be reaching a far-off audience with different computer configurations. In order for documents to be interpreted correctly, authors should include in their documents information about the natural language and direction of the text, how the document is encoded, and other issues related to internationalization.

Help user agents with incremental RENDERING
By carefully designing their tables and making use of new table features in HTML 4.0, authors can help user agents render documents more quickly. Authors can learn how to design tables for incremental rendering (see the TABLE element). Implementors should consult the notes on tables [p.317] in the appendix for information on incremental algorithms.

following general principles when working with HTML 4.0.

Separate structure and presentation
HTML has its roots in SGML which has always been a language for the specification of structural markup. As HTML matures, more and more of its presentational elements and attributes are being replaced by other mechanisms, in particular style sheets. Experience has shown that separating the structure of a document from its presentational aspects reduces the cost of serving a wide range of platforms, media, etc., and facilitates document revisions.

Consider universal accessibility to the Web
To make the Web more accessible to everyone, notably those with disabilities, authors should consider how their documents may be rendered on a variety of platforms: speech-based browsers, braille-readers, etc. We do not recommend that authors limit their creativity, only that they consider alternate renderings in their design. HTML offers a number of mechanisms to this end (e.g., the alt attribute, the accesskey attribute, etc.)

Furthermore, authors should keep in mind that their documents may be reaching a far-off audience with different computer configurations. In order for documents to be interpreted correctly, authors should include in their documents information about the natural language and direction of the text, how the document is encoded, and other issues related to internationalization.

Help user agents with incremental rendering
By carefully designing their tables and making use of new table features in HTML 4.0, authors can help user agents render documents more quickly. Authors can learn how to design tables for incremental rendering (see the TABLE element). Implementors should consult the notes on tables [p.317] in the appendix for information on incremental algorithms.

<DIV id="header">
<h1>Monday Times</h1>
</div>
.
.
.
<div id="footer">
<p>&COPY; JAVATPOINT. All RIGHTS reserved.</p> 
</div>

<div id="header">
<h1>Monday Times</h1>
</div>
.
.
.
<div id="footer">
<p>&copy; JavaTpoint. All rights reserved.</p> 
</div>

A typical WEB page has headers, footers, navigation, central AREA and side bars. Now if we want to represent the same in HTML 4 with proper names to the HTML section we would probably use a DIV tag.

But in HTML 5 they have made it more clear by creating element names for those sections which makes your HTML more readable.

Below are more DETAILS of the HTML 5 elements which form the page structure.
•<header>: Represents header data of HTML.
•<footer>: Footer section of the page.
•<nav>: Navigation elements in the page.
•<article>: Self-contained content.
•<section>: Used inside article to DEFINE sections or group content in to sections.
•<aside>: Represent side bar contents of a page.

A typical web page has headers, footers, navigation, central area and side bars. Now if we want to represent the same in HTML 4 with proper names to the HTML section we would probably use a DIV tag.

But in HTML 5 they have made it more clear by creating element names for those sections which makes your HTML more readable.

Below are more details of the HTML 5 elements which form the page structure.
•<header>: Represents header data of HTML.
•<footer>: Footer section of the page.
•<nav>: Navigation elements in the page.
•<article>: Self-contained content.
•<section>: Used inside article to define sections or group content in to sections.
•<aside>: Represent side bar contents of a page.

Frames allow an author to divide a browser window into MULTIPLE (rectangular) regions. Multiple documents can be displayed in a single window, each within its own frame. GRAPHICAL browsers allow these frames to be scrolled independently of each other, and links can update the document displayed in one frame without affecting the others.

You can't just "add frames" to an EXISTING document. Rather, you must create a frameset document that defines a particular combination of frames, and then display your content documents inside those frames. The frameset document should also include alternative non-framed content in a NOFRAMES element. The HTML 4 frames model has significant DESIGN flaws that cause usability problems for web users. Frames should be used only with great care.

Frames allow an author to divide a browser window into multiple (rectangular) regions. Multiple documents can be displayed in a single window, each within its own frame. Graphical browsers allow these frames to be scrolled independently of each other, and links can update the document displayed in one frame without affecting the others.

You can't just "add frames" to an existing document. Rather, you must create a frameset document that defines a particular combination of frames, and then display your content documents inside those frames. The frameset document should also include alternative non-framed content in a NOFRAMES element. The HTML 4 frames model has significant design flaws that cause usability problems for web users. Frames should be used only with great care.

Removing the border around frames involves both not drawing the frame borders and ELIMINATING the space between the frames. The most widely supported way to display borderless frames is <FRAMESET ... BORDER=0 FRAMEBORDER=0 FRAMESPACING=0>.

Note that these attributes are proprietary and not part of the HTML 4.01 specifications. (HTML 4.01 does define the FRAMEBORDER attribute for the FRAME element, but not for the FRAMESET element.) Also, removing the border around a frame makes it DIFFICULT to RESIZE it, as this border is also USED in most GUIs to change the size of the frame.

Removing the border around frames involves both not drawing the frame borders and eliminating the space between the frames. The most widely supported way to display borderless frames is <FRAMESET ... BORDER=0 FRAMEBORDER=0 FRAMESPACING=0>.

Note that these attributes are proprietary and not part of the HTML 4.01 specifications. (HTML 4.01 does define the FRAMEBORDER attribute for the FRAME element, but not for the FRAMESET element.) Also, removing the border around a frame makes it difficult to resize it, as this border is also used in most GUIs to change the size of the frame.