Middle Column
Width = 60%. Page 2.
What astounds me is my personal stupidity in pursuit of the so called
If any of the 3 columns exceed the height of the available viewing area it will require vertical-scrolling, both down and up, by the viewer, to read columns from top to bottom with continuity. Scroll-Down then Scroll-Up in order to view is highly illogical to me. A real mess for printing also.
Scroll to the bottom of Left Column ( L-Col ) then read middle and right while bottom of left is visible, line 69.
AOL Users: If unable to read 69. at bottom of left column, simply maximize your inner screen, then scroll down.
The pursuit of exactly what is Positioned:CSS is my only justification for this experiment.
MicroSoft Internet Explorer and Opera 6.x allow me to read and write via JavaScript attributes of items which are declared to be position:relative; and position:absolute; via CSS.
NetScape 6.x and Mozilla ( GECKO ) seem to treat Relative Positioned CSS Attributes as NOT positioned and only allow me to read and write Absolute Positioned CSS Attributes? Therefore, some logic for the pursuit.
When I first read the "specs", it said attributes of items positioned by css are "dynamic" and may be repositioned. No distinction that relative was not to be considered positioned in this regard.
Note position of <hr> in each column for later discussion.
Also, notice 1% vertical bar in horizontal seperation of middle and right is not visible as on Page 1 with MSIE and Opera.
Next: Page 3 - Link is in right column ( R-Col ).