Wednesday 26th of July 2017 10:44:17 AM

left

#left {
position: absolute;
left: 2%;
width: 22%;
top: 106px;
background-color: #ffffff;
}

Attention

These pages use certain CSS definitions that are unsupported by older browsers.
more nice and free css templates


css



middle right

#content {
position: absolute;
left: 25%;
width: 50%;
top: 106px;
background-color: #ffffff;
overflow: auto;
}

overflow: auto;

With overflow: auto; With overflow: you can determine how overflowing content should be treated.

Values

visible = The element gets expanded to show the entire content.
hidden  = The content will be cut if it overflows.
scroll  = The browser should offer scroll bars.
auto    = The browser should decide how to render the element. Scroll bars are allowed.

Older browsers do not know support this property.
IE does not support overflow:visible



shorthand property: background. This property cantake a single value from each of the other background properties, inliterally any order.

background

BODY {background-color: white; background-image: url(yinyang.gif);background-position: top left; background-repeat: repeat-y;background-attachment: fixed;}BODY {background: white url(yinyang.gif) top left repeat-y fixed;}
P {margin: -10%;}

Figure 7-20 illustrates the consequences of such arule, where the amount by which paragraphs overlap each other andspill beyond the browser window is entirely dependent on the width ofthe window itself -- and the wider the window, the worse thesituation becomes.

Figure 7-20

Figure 7-20. The dangers of document-wide negative-margin rules

Using negative margins with block-level elements incomplete, the specification simply avoids the problem. In addition, this allows user agents to employ their own hyphenation rules, and improve them over time without being hindered by anything in the CSS specification.

Since there is no hyphenation in CSS, user agents are unlikely to be able to perform any automatic hyphenation. Thus, justified text will very likely be less attractive under CSS than it might be in print, especially when elements become so narrow that only a few words canserver names and domains.

The path and filename in a URL are typically specified from the rootof the web-server directory, which is some subdirectory of the server'slocal file system.  For security reasons, browsers can't access stuffoutside the web-server directory. 

URLs can specify files by  relative or absolute path. A relative URL specifies a file relative to the location of the file containingthe URL.  An absolute URL specifies the full server name and pathfrom the root directory of the web-server.  Suppose your web pageis http://www.taxidermy.org/~mad_dog/homepage.html and it includes

SAX, DOM and XML are very developer friendly because developers are going to decide whether this technology will be adopted by the majority and become a successful effort towards the goal of interoperable, platform, and device independent computing.

XML is web enabled

XML is derived from SGML, and so was HTML. So in essence, the current infrastructure available today to deal with HTML content can be re-used to work with XML. This is a very big advantage towards delivering XML content using the software and networking infrastructure already in place today. This should be a big plus in considering XML for use in any of your projects, because XML naturally lends itself to being used over the web.

Even if clients don't support XML natively, it is not a big hindrance. In fact, Java with Servlets (on the server side) can convert XML with stylesheets to generate plain HTML that can be displayed in all web browsers.