Explore topic-wise InterviewSolutions in .

Setting EnableViewStateMac=true is a security MEASURE that allows ASP.NET to ensure that the viewstate for a page has not been tampered with. If on Postback, the ASP.NET framework detects that there has been a change in the value of viewstate that was sent to the BROWSER, it raises an error - Validation of viewstate MAC failed. 

Use <%@ Page EnableViewStateMac="true"%> to set it to true (the DEFAULT value, if this attribute is not specified is also true) in an aspx page.

Setting EnableViewStateMac=true is a security measure that allows ASP.NET to ensure that the viewstate for a page has not been tampered with. If on Postback, the ASP.NET framework detects that there has been a change in the value of viewstate that was sent to the browser, it raises an error - Validation of viewstate MAC failed. 

Use <%@ Page EnableViewStateMac="true"%> to set it to true (the default value, if this attribute is not specified is also true) in an aspx page.

VIEWSTATE is specific to a page in a SESSION. Session state refers to user specific data that can be accessed across all PAGES in the WEB APPLICATION.

ViewState is specific to a page in a session. Session state refers to user specific data that can be accessed across all pages in the web application.

The best SITES are the ONES that use JavaScript so transparently, that I'm not aware that there is any scripting on the PAGE. The worst sites are those that try to IMPRESS me with how MUCH scripting is on the page.

The best sites are the ones that use JavaScript so transparently, that I'm not aware that there is any scripting on the page. The worst sites are those that try to impress me with how much scripting is on the page.

One of the reasons JavaScript has the word "script" in it is that as a programming language, the vocabulary of the core language is compact compared to full-fledged programming languages. If you already PROGRAM in JAVA or C, you actually have to unlearn some concepts that had been beaten into you. For example, JavaScript is a loosely typed language, which means that a variable doesn't care if it's holding a string, a number, or a REFERENCE to an object; the same variable can even change what type of data it holds while a script runs.

The other part of JavaScript implementation in browsers that makes it easier to learn is that most of the objects you script are pre-defined for the author, and they largely represent PHYSICAL things you can see on a PAGE: a text box, an image, and so on. It's easier to say, "OK, these are the things I'm working with and I'll use scripting to make them do such and such," instead of having to dream up the user interface, conceive of and code objects, and handle the interaction between objects and users. With scripting, you tend to write a _lot_ less code.

One of the reasons JavaScript has the word "script" in it is that as a programming language, the vocabulary of the core language is compact compared to full-fledged programming languages. If you already program in Java or C, you actually have to unlearn some concepts that had been beaten into you. For example, JavaScript is a loosely typed language, which means that a variable doesn't care if it's holding a string, a number, or a reference to an object; the same variable can even change what type of data it holds while a script runs.

The other part of JavaScript implementation in browsers that makes it easier to learn is that most of the objects you script are pre-defined for the author, and they largely represent physical things you can see on a page: a text box, an image, and so on. It's easier to say, "OK, these are the things I'm working with and I'll use scripting to make them do such and such," instead of having to dream up the user interface, conceive of and code objects, and handle the interaction between objects and users. With scripting, you tend to write a _lot_ less code.

Breaking is POSSIBLE within a string STATEMENT by USING a BACKSLASH at the end but not within any other javascript statement.that is ,
document.write("Hello WORLD");

is possible but not document.write
("hello world");

Breaking is possible within a string statement by using a backslash at the end but not within any other javascript statement.that is ,
document.write("Hello world");

is possible but not document.write
("hello world");

A prompt box ALLOWS the USER to enter INPUT by providing a TEXT box.

A prompt box allows the user to enter input by providing a text box.

An ALERT box displays only one BUTTON which is the OK button WHEREAS the Confirm box displays TWO buttons namely OK and cancel.

An alert box displays only one button which is the OK button whereas the Confirm box displays two buttons namely OK and cancel.

This can be achieved by using the following TAG between HEAD tags or between BODY tags.

<script SRC="abc.js"></script>

 where abc.js is the external javscript file to be accessed.

This can be achieved by using the following tag between head tags or between body tags.

<script src="abc.js"></script>

 where abc.js is the external javscript file to be accessed.

<script&GT; FUNCTION setFocus() { if(focusElement != NULL) { document.forms[0].elements["myelementname"].FOCUS(); } } </script>

<script> function setFocus() { if(focusElement != null) { document.forms[0].elements["myelementname"].focus(); } } </script>

VAR checkedP = window.document.getElementById("myCheckBox").CHECKED;

var checkedP = window.document.getElementById("myCheckBox").checked;

USE the "VALUE" PROPERTY. 
VAR myValue = window.document.getElementById("MyTextBox").value;

Use the "value" property. 
var myValue = window.document.getElementById("MyTextBox").value;

Web-garden - An IIS6.0 feature where you can configure an application POOL as a web-garden and also specify the number of worker processes for that pool. It can help improve performance in some cases. 

Web-farm - a general term referring to a cluster of physically separate machines, each running a web-server for SCALABILITY and performance (contrast this with web-garden which refers to MULTIPLE processes on one single PHYSICAL machine).

Web-garden - An IIS6.0 feature where you can configure an application pool as a web-garden and also specify the number of worker processes for that pool. It can help improve performance in some cases. 

Web-farm - a general term referring to a cluster of physically separate machines, each running a web-server for scalability and performance (contrast this with web-garden which refers to multiple processes on one single physical machine).

Since 1 is a STRING, EVERYTHING is a string, so the RESULT is 124. 

Since 1 is a string, everything is a string, so the result is 124. 

• &AMP;&
• ||
• !

Browser version incompatibility is the biggest problem. It requires knowing how each scriptable browser version implements its object model. You see, the incompatibility rarely has to do with the core JavaScript language (although there have been improvements to the language over time); the bulk of incompatibility issues have to do with the object models that each browser version implements. For EXAMPLE, scripters who started out with Navigator 3 implemented the image rollover because it looked cool. But they were dismayed to find out that the image object wasn't scriptable in Internet Explorer 3 or Navigator 2. While there are easy workarounds to make this FEATURE work on newer browsers without disturbing older ones, it was a painful LEARNING experience for many. 

The second biggest can of worms is scripting CONNECTIONS between MULTIPLE windows. A lot of scripters like to have little windows pop up with navigation bars or some such gizmos. But the object models, especially in the older browser versions, don't make it easy to work with these windows the minute you put a user in front of them--users who can manually close windows or change their stacking order. More recently, a glitch in some uninstall routines for Windows 95 applications can disturb vital parts of the system Registry that Internet Explorer 4 requires for managing multiple windows. A scripter can't work around this problem, because it's not possible to detect the problem in a user's machine. I tend to avoid multiple windows that interact with each other.

Browser version incompatibility is the biggest problem. It requires knowing how each scriptable browser version implements its object model. You see, the incompatibility rarely has to do with the core JavaScript language (although there have been improvements to the language over time); the bulk of incompatibility issues have to do with the object models that each browser version implements. For example, scripters who started out with Navigator 3 implemented the image rollover because it looked cool. But they were dismayed to find out that the image object wasn't scriptable in Internet Explorer 3 or Navigator 2. While there are easy workarounds to make this feature work on newer browsers without disturbing older ones, it was a painful learning experience for many. 

The second biggest can of worms is scripting connections between multiple windows. A lot of scripters like to have little windows pop up with navigation bars or some such gizmos. But the object models, especially in the older browser versions, don't make it easy to work with these windows the minute you put a user in front of them--users who can manually close windows or change their stacking order. More recently, a glitch in some uninstall routines for Windows 95 applications can disturb vital parts of the system Registry that Internet Explorer 4 requires for managing multiple windows. A scripter can't work around this problem, because it's not possible to detect the problem in a user's machine. I tend to avoid multiple windows that interact with each other.

 The best place to start is SOMETHING called the meta- which provides a high-level OVERVIEW of the JavaScript help available on the Net. 

For INTERACTIVE help with specific problems, nothing beats the primary JavaScript Usenet newsgroup, comp.lang.javascript. NETSCAPE and Microsoft also have vendor-specific developer discussion groups as WELL as detailed documentation for the scripting and object model implementations.

 The best place to start is something called the meta- which provides a high-level overview of the JavaScript help available on the Net. 

For interactive help with specific problems, nothing beats the primary JavaScript Usenet newsgroup, comp.lang.javascript. Netscape and Microsoft also have vendor-specific developer discussion groups as well as detailed documentation for the scripting and object model implementations.

javascript code can be embedded in a web PAGE between <script langugage="javascript"&GT;</script> tags

javascript code can be embedded in a web page between <script langugage="javascript"></script> tags

No.java and javascript are two DIFFERENT languages.
Java is a powerful OBJECT - oriented PROGRAMMING language like C++,C whereas Javascript is a client-side SCRIPTING language with some limitations.

No.java and javascript are two different languages.
Java is a powerful object - oriented programming language like C++,C whereas Javascript is a client-side scripting language with some limitations.

Yes.Since JAVASCRIPT is a client-side SCRIPT it does require the web server's help for its computation,so it is always FASTER than any server-side script LIKE ASP,PHP,etc..

Yes.Since javascript is a client-side script it does require the web server's help for its computation,so it is always faster than any server-side script like ASP,PHP,etc..

The "Access Denied" ERROR in any browser is due to the following reason.
A javascript in one window or FRAME is tries to access another window or frame whose document's domain is DIFFERENT from the document CONTAINING the script.

The "Access Denied" error in any browser is due to the following reason.
A javascript in one window or frame is tries to access another window or frame whose document's domain is different from the document containing the script.

It is true, TEXT you last copied for pasting (copy & paste) can be STOLEN when you visit web sites USING a combination of JAVASCRIPT and ASP (or PHP, or CGI) to write your possible sensitive data to a database on another server.

It is true, text you last copied for pasting (copy & paste) can be stolen when you visit web sites using a combination of JavaScript and ASP (or PHP, or CGI) to write your possible sensitive data to a database on another server.

1. To REMOVE an ITEM from a LIST set it to null.
mySelectObject.options[3] = null; 

2. To truncate a list set its length to the maximum size you desire.
mySelectObject.length = 2; 

3. To delete all options in a select object set the length to 0. 
mySelectObject.leng

1. To remove an item from a list set it to null.
mySelectObject.options[3] = null; 

2. To truncate a list set its length to the maximum size you desire.
mySelectObject.length = 2; 

3. To delete all options in a select object set the length to 0. 
mySelectObject.leng

• GET: PARAMETERS are passed in the querystring. Maximum amount of DATA that can be sent via the GET method is limited to about 2kb.
• POST: Parameters are passed in the request body. There is no limit to the amount of data that can be TRANSFERRED using POST. HOWEVER, there are LIMITS on the maximum amount of data that can be transferred in one name/value pair.

All VARIABLES are of OBJECT TYPE in JAVASCRIPT. 

All variables are of object type in JavaScript. 

USE WINDOW.opener to REFER to the MAIN window from pop-ups.

Use window.opener to refer to the main window from pop-ups.

It’s a number in JAVASCRIPT, DERIVED by dividing negative number by ZERO.

It’s a number in JavaScript, derived by dividing negative number by zero.

RETURN TRUE if the ARGUMENT is not a NUMBER.

Return true if the argument is not a number.

Fragmentation of the installed base of browsers will only get worse. By definition, it can never improve unless absolutely everyone on the PLANET threw away their old browsers and upgraded to the latest gee-whiz versions. But even then, there are plenty of discrepancies between the scriptability of the latest NETSCAPE Navigator and Microsoft Internet Explorer. 

The situation makes scripting a challenge, especially for newcomers who may not be aware of the limitations of earlier browsers. A lot of effort in my books and ancillary material goes toward helping scripters know what features work in which browsers and how to either workaround limitations in earlier browsers or raise the compatibility COMMON denominator. 

Designing scripts for a Web site requires making some hard decisions about if, when, and how to implement the advantages scripting OFFERS a page to your AUDIENCE. For public Web sites, I recommend using scripting in an additive way: let sufficient content stand on its own, but let scriptable browser users receive an enhanced experience, preferably with the same HTML document.

Fragmentation of the installed base of browsers will only get worse. By definition, it can never improve unless absolutely everyone on the planet threw away their old browsers and upgraded to the latest gee-whiz versions. But even then, there are plenty of discrepancies between the scriptability of the latest Netscape Navigator and Microsoft Internet Explorer. 

The situation makes scripting a challenge, especially for newcomers who may not be aware of the limitations of earlier browsers. A lot of effort in my books and ancillary material goes toward helping scripters know what features work in which browsers and how to either workaround limitations in earlier browsers or raise the compatibility common denominator. 

Designing scripts for a Web site requires making some hard decisions about if, when, and how to implement the advantages scripting offers a page to your audience. For public Web sites, I recommend using scripting in an additive way: let sufficient content stand on its own, but let scriptable browser users receive an enhanced experience, preferably with the same HTML document.

JavaScript allows a Web page to PERFORM "if-then" kinds of decisions based on browser VERSION, operating system, user input, and, in more recent browsers, details about the screen size in which the browser is running. While a server CGI program can make some of those same kinds of decisions, not everyone has access to or the EXPERTISE to create CGI programs. For example, an experienced CGI programmer can examine information about the browser whenever a request for a page is made; thus a server so equipped might serve up one page for Navigator users and a different page for Internet Explorer users. Beyond browser and operating system version, a CGI program can't know more about the environment. But a JavaScript-enhanced page can instruct the browser to RENDER only certain content based on the browser, operating system, and even the screen size. 

Scripting can even go further if the page author desires. For example, the author may include a preference screen that lets the user determine the desired background and text color combination. A script can save this information on the client in a well-regulated local file called a cookie. The next time the user comes to the site, scripts in its PAGES look to the cookie info and render the page in the color combination selected previously. The server is none the wiser, nor does it have to store any visitor-specific information.

JavaScript allows a Web page to perform "if-then" kinds of decisions based on browser version, operating system, user input, and, in more recent browsers, details about the screen size in which the browser is running. While a server CGI program can make some of those same kinds of decisions, not everyone has access to or the expertise to create CGI programs. For example, an experienced CGI programmer can examine information about the browser whenever a request for a page is made; thus a server so equipped might serve up one page for Navigator users and a different page for Internet Explorer users. Beyond browser and operating system version, a CGI program can't know more about the environment. But a JavaScript-enhanced page can instruct the browser to render only certain content based on the browser, operating system, and even the screen size. 

Scripting can even go further if the page author desires. For example, the author may include a preference screen that lets the user determine the desired background and text color combination. A script can save this information on the client in a well-regulated local file called a cookie. The next time the user comes to the site, scripts in its pages look to the cookie info and render the page in the color combination selected previously. The server is none the wiser, nor does it have to store any visitor-specific information.

document.bgcolor PROPERTY can be SET to any APPROPRIATE COLOR.

document.bgcolor property can be set to any appropriate color.

Generation of HTML PAGES on-the-fly without accessing the Web server. The user can be given control over the browser like User input validation Simple computations can be performed on the client's MACHINE The user's browser, OS, screen size, etc. can be detected DATE and Time HANDLING

Generation of HTML pages on-the-fly without accessing the Web server. The user can be given control over the browser like User input validation Simple computations can be performed on the client's machine The user's browser, OS, screen size, etc. can be detected Date and Time Handling

Include the name of the frame in the target ATTRIBUTE of the HYPERLINK. <a HREF=”mypage.htm” target=”myframe”>>My Page</a>

Include the name of the frame in the target attribute of the hyperlink. <a href=”mypage.htm” target=”myframe”>>My Page</a>

We can declare an array like this 
var SCRIPTS = new Array(); 
We can add elements to this array like this
scripts[0] = "PHP";
scripts[1] = "ASP";
scripts[2] = "JavaScript";
scripts[3] = "HTML";
Now our array scrips has 4 elements INSIDE it and we can print or access them by using their index number. Note that index number starts from 0. To get the third ELEMENT of the array we have to use the index number 2 . Here is the way to get the third element of an array. 
document.write(scripts[2]); 
We also can create an array like this 
var no_array = new Array(21, 22, 23, 24, 25);

We can declare an array like this 
var scripts = new Array(); 
We can add elements to this array like this
scripts[0] = "PHP";
scripts[1] = "ASP";
scripts[2] = "JavaScript";
scripts[3] = "HTML";
Now our array scrips has 4 elements inside it and we can print or access them by using their index number. Note that index number starts from 0. To get the third element of the array we have to use the index number 2 . Here is the way to get the third element of an array. 
document.write(scripts[2]); 
We also can create an array like this 
var no_array = new Array(21, 22, 23, 24, 25);

Use the parseInt() function, that takes a string as the first parameter, and the BASE as a SECOND parameter. So to convert hexadecimal 3F to decimal, use parseInt ("3F", 16);

Use the parseInt() function, that takes a string as the first parameter, and the base as a second parameter. So to convert hexadecimal 3F to decimal, use parseInt ("3F", 16);

NUMBER, String, BOOLEAN, Function, Object, Null, UNDEFINED.

Number, String, Boolean, Function, Object, Null, Undefined.

<SCRIPT type="text/javascript">
var numbers = ["one", "TWO", "three", "four"];
numbers.unshift("zero");
document.write(" "+numbers.shift());
document.write(" "+numbers.shift());
document.write(" "+numbers.shift());
</script>
This produces
zero one two
shift, unshift, push, and pop MAY be used on the same array. QUEUES are EASILY implemented using combinations.

<script type="text/javascript">
var numbers = ["one", "two", "three", "four"];
numbers.unshift("zero");
document.write(" "+numbers.shift());
document.write(" "+numbers.shift());
document.write(" "+numbers.shift());
</script>
This produces
zero one two
shift, unshift, push, and pop may be used on the same array. Queues are easily implemented using combinations.

The POP() and push() functions turn a harmless array into a stack
<SCRIPT type="text/javascript">
var numbers = ["ONE", "two", "THREE", "four"];
numbers.push("FIVE");
numbers.push("six");
document.write(numbers.pop());
document.write(numbers.pop());
document.write(numbers.pop());
</script>
This produces
sixfivefour

The pop() and push() functions turn a harmless array into a stack
<script type="text/javascript">
var numbers = ["one", "two", "three", "four"];
numbers.push("five");
numbers.push("six");
document.write(numbers.pop());
document.write(numbers.pop());
document.write(numbers.pop());
</script>
This produces
sixfivefour

The FOLLOWING example illustrates this
It CREATES a function called square with ARGUMENT X and RETURNS x multiplied by itself.
var square = new Function ("x","return x*x");

The following example illustrates this
It creates a function called square with argument x and returns x multiplied by itself.
var square = new Function ("x","return x*x");

Continue statement CONTINUES the current loop (if label not SPECIFIED) in a NEW iteration WHEREAS BREAK statement exits the current loop.

Continue statement continues the current loop (if label not specified) in a new iteration whereas break statement exits the current loop.

A HYPERTEXT link is a special TAG that links one page to another page or RESOURCE. If you click the link, the browser jumps to the link's DESTINATION.

A hypertext link is a special tag that links one page to another page or resource. If you click the link, the browser jumps to the link's destination.

HTML Code:
<HTML>
<HEAD>
<TITLE>This is my page title! </TITLE>
</HEAD>
<BODY>
This is my message to the world!
</BODY>
</HTML> 
Browser DISPLAY:
This is my message to the world!

HTML Code:
<HTML>
<HEAD>
<TITLE>This is my page title! </TITLE>
</HEAD>
<BODY>
This is my message to the world!
</BODY>
</HTML> 
Browser Display:
This is my message to the world!

In HTML, a tag tells the browser what to do. When you write an HTML page, you ENTER TAGS for many reasons -- to change the appearance of TEXT, to show a graphic, or to make a LINK to another page.

In HTML, a tag tells the browser what to do. When you write an HTML page, you enter tags for many reasons -- to change the appearance of text, to show a graphic, or to make a link to another page.

There are two basic techniques for updating multiple frames with a single link: The HTML-based technique links to a new FRAMESET document that specifies the new combination of frames. The JavaScript-based solution uses the onClick attribute of the link to update the additional frame (or frames).
The HTML-based technique can link to a new frameset document with the TARGET="_top" attribute (replacing the entire frameset). However, there is an ALTERNATIVE if the frames to be updated are part of a NESTED frameset. In the initial frameset document, use a secondary frameset document to define the nested frameset. For example:
<frameset cols="*,3*">
<frame SRC="contents.html" name="Contents">
<frame src="frameset2.html" name="Display">
<noframes>
<!-- Alternative non-framed version -->
</body></noframes>
</frameset>
A link can now use the TARGET="Display" attribute to replace simultaneously all the frames defined by the frameset2.html document. 
The JavaScript-based solution uses the onClick attribute of the link to PERFORM the secondary update. For example: 
<a href="URL1" target="Frame1" onClick="top.Frame2.location='URL2';">Update frames 
The link will update Frame1 with URL1 normally. If the reader's browser supports JavaScript (and has it enabled), then Frame2 will also be updated (with URL2).

There are two basic techniques for updating multiple frames with a single link: The HTML-based technique links to a new frameset document that specifies the new combination of frames. The JavaScript-based solution uses the onClick attribute of the link to update the additional frame (or frames).
The HTML-based technique can link to a new frameset document with the TARGET="_top" attribute (replacing the entire frameset). However, there is an alternative if the frames to be updated are part of a nested frameset. In the initial frameset document, use a secondary frameset document to define the nested frameset. For example:
<frameset cols="*,3*">
<frame src="contents.html" name="Contents">
<frame src="frameset2.html" name="Display">
<noframes>
<!-- Alternative non-framed version -->
</body></noframes>
</frameset>
A link can now use the TARGET="Display" attribute to replace simultaneously all the frames defined by the frameset2.html document. 
The JavaScript-based solution uses the onClick attribute of the link to perform the secondary update. For example: 
<a href="URL1" target="Frame1" onClick="top.Frame2.location='URL2';">Update frames 
The link will update Frame1 with URL1 normally. If the reader's browser supports JavaScript (and has it enabled), then Frame2 will also be updated (with URL2).

When the sub-documents of a frameset state are accessed directly, they appear without the context of the surrounding frameset.
If the reader's browser has JavaScript support enabled, the FOLLOWING script will RESTORE the frameset:
<SCRIPT TYPE="text/javascript">
if (parent.location.href == self.location.href) {
if (window.location.href.replace)
window.location.replace('frameset.html');
else
// causes problems with back button, but works
window.location.href = 'frameset.html';
}
</SCRIPT> 
A more universal approach is a "restore frames" link:
<A HREF="frameset.html" TARGET="_top">Restore Frames 
Note that in EITHER CASE, you must have a separate frameset document for every content document. If you link to the default frameset document, then your reader will get the default content document, rather than the content document he/she was trying to access. These frameset documents should be generated automatically, to AVOID the tedium and inaccuracy of creating them by hand. 
Note that you can work around the problem with bookmarking frameset states by linking to these separate frameset documents using TARGET="_top", rather than linking to the individual content documents.

When the sub-documents of a frameset state are accessed directly, they appear without the context of the surrounding frameset.
If the reader's browser has JavaScript support enabled, the following script will restore the frameset:
<SCRIPT TYPE="text/javascript">
if (parent.location.href == self.location.href) {
if (window.location.href.replace)
window.location.replace('frameset.html');
else
// causes problems with back button, but works
window.location.href = 'frameset.html';
}
</SCRIPT> 
A more universal approach is a "restore frames" link:
<A HREF="frameset.html" TARGET="_top">Restore Frames 
Note that in either case, you must have a separate frameset document for every content document. If you link to the default frameset document, then your reader will get the default content document, rather than the content document he/she was trying to access. These frameset documents should be generated automatically, to avoid the tedium and inaccuracy of creating them by hand. 
Note that you can work around the problem with bookmarking frameset states by linking to these separate frameset documents using TARGET="_top", rather than linking to the individual content documents.

There was a tag proposed for HTML 3.0, but it was never adopted by any major browser and the draft SPECIFICATION has now expired. You can simulate a tab or indent in various ways, INCLUDING using a transparent GIF, but none are quite as satisfactory or widely supported as an official tag would be.

My page looks good on one browser, but not on another. There are slight differences between BROWSERS, such as Netscape Navigator and Microsoft Internet Explorer, in areas such as page MARGINS. The only real answer is to use standard HTML tags whenever possible, and view your pages in multiple browsers to see how they look.

There was a tag proposed for HTML 3.0, but it was never adopted by any major browser and the draft specification has now expired. You can simulate a tab or indent in various ways, including using a transparent GIF, but none are quite as satisfactory or widely supported as an official tag would be.

My page looks good on one browser, but not on another. There are slight differences between browsers, such as Netscape Navigator and Microsoft Internet Explorer, in areas such as page margins. The only real answer is to use standard HTML tags whenever possible, and view your pages in multiple browsers to see how they look.

The fundamental problem with the design of frames is that framesets create states in the BROWSER that are not addressable. Once any of the frames within a frameset changes from its default CONTENT, there is no longer a way to address the current state of the frameset. It is difficult to bookmark - and impossible to LINK or index - such a frameset state. It is impossible to reference such a frameset state in other media. When the sub-documents of such a frameset state are accessed directly, they appear without the context of the surrounding frameset. Basic browser functions (e.g., printing, moving forwards/backwards in the browser's history) behave differently with framesets. Also, browsers cannot identify which frame should have focus, which affects scrolling, searching, and the USE of KEYBOARD shortcuts in general. 

Furthermore, frames focus on layout rather than on information structure, and many authors of framed sites neglect to provide useful alternative content in the NOFRAMES element. Both of these factors cause accessibility problems for browsers that differ significantly from the author's expectations and for search engines.

The fundamental problem with the design of frames is that framesets create states in the browser that are not addressable. Once any of the frames within a frameset changes from its default content, there is no longer a way to address the current state of the frameset. It is difficult to bookmark - and impossible to link or index - such a frameset state. It is impossible to reference such a frameset state in other media. When the sub-documents of such a frameset state are accessed directly, they appear without the context of the surrounding frameset. Basic browser functions (e.g., printing, moving forwards/backwards in the browser's history) behave differently with framesets. Also, browsers cannot identify which frame should have focus, which affects scrolling, searching, and the use of keyboard shortcuts in general. 

Furthermore, frames focus on layout rather than on information structure, and many authors of framed sites neglect to provide useful alternative content in the NOFRAMES element. Both of these factors cause accessibility problems for browsers that differ significantly from the author's expectations and for search engines.

The only way to have a FRAME with a vertical scrollbar but without a horizontal scrollbar is to DEFINE the frame with SCROLLING="AUTO" (the default), and to have content that does not require horizontal scrolling. There is no way to specify that a frame should have one scrollbar but not the other. Using SCROLLING="yes" will force SCROLLBARS in both DIRECTIONS (even when they aren't needed), and using SCROLLING="no" will inhibit all scrollbars (even when scrolling is necessary to access the frame's content). There are no other values for the SCROLLING attribute.

The only way to have a frame with a vertical scrollbar but without a horizontal scrollbar is to define the frame with SCROLLING="auto" (the default), and to have content that does not require horizontal scrolling. There is no way to specify that a frame should have one scrollbar but not the other. Using SCROLLING="yes" will force scrollbars in both directions (even when they aren't needed), and using SCROLLING="no" will inhibit all scrollbars (even when scrolling is necessary to access the frame's content). There are no other values for the SCROLLING attribute.

If you are the author, this is easy. You only have to add the TARGET attribute to the link that takes readers to the intended 'outside' DOCUMENT. Give it the value of _top. 

In many current browsers, it is not possible to display a frame in the FULL browser window, at least not very easily. The reader would need to copy the URL of the DESIRED frame and then REQUEST that URL manually. 

I would recommend that authors who want to OFFER readers this option add a link to the document itself in the document, with the TARGET attribute set to _top so the document displays in the full window if the link is followed.

If you are the author, this is easy. You only have to add the TARGET attribute to the link that takes readers to the intended 'outside' document. Give it the value of _top. 

In many current browsers, it is not possible to display a frame in the full browser window, at least not very easily. The reader would need to copy the URL of the desired frame and then request that URL manually. 

I would recommend that authors who want to offer readers this option add a link to the document itself in the document, with the TARGET attribute set to _top so the document displays in the full window if the link is followed.

If there is no existing frame with the name you used for the TARGET attribute, then a new browser window will be OPENED, and this window will be assigned the name you used. Furthermore, TARGET="_blank" will open a new, unnamed browser window. 

In HTML 4, the TARGET attribute value is case-insensitive, so that abc and ABC both refer to the same frame/window, and _top and _TOP both have the same meaning. However, most browsers treat the TARGET attribute value as case-sensitive and do not recognize ABC as being the same as abc, or _TOP as having the SPECIAL meaning of _top. 

Also, some browsers include a security FEATURE that prevents documents from being hijacked by third-party framesets. In these browsers, if a document's link TARGETS a frame defined by a frameset document that is located on a different server than the document itself, then the link opens in a new window instead.

If there is no existing frame with the name you used for the TARGET attribute, then a new browser window will be opened, and this window will be assigned the name you used. Furthermore, TARGET="_blank" will open a new, unnamed browser window. 

In HTML 4, the TARGET attribute value is case-insensitive, so that abc and ABC both refer to the same frame/window, and _top and _TOP both have the same meaning. However, most browsers treat the TARGET attribute value as case-sensitive and do not recognize ABC as being the same as abc, or _TOP as having the special meaning of _top. 

Also, some browsers include a security feature that prevents documents from being hijacked by third-party framesets. In these browsers, if a document's link targets a frame defined by a frameset document that is located on a different server than the document itself, then the link opens in a new window instead.

Use an IMG element. The SRC attribute specifies the location of the image. The ALT attribute PROVIDES alternate text for those not LOADING IMAGES. For EXAMPLE:
<img src="logo.gif" alt="ACME Products">

Use an IMG element. The SRC attribute specifies the location of the image. The ALT attribute provides alternate text for those not loading images. For example:
<img src="logo.gif" alt="ACME Products">