|
|
| Line 55: |
Line 55: |
| | <TD WIDTH=40><BR></TD> | | <TD WIDTH=40><BR></TD> |
| | <TD> | | <TD> |
| - | <p>
| + | |
| - |
| + | |
| - | </p><p>
| + | |
| - |
| + | |
| - | </p>
| + | |
| | <div id="floatlayer" style="width:50%;background:#d0d0ff;border:solid black 1px;padding:5px"> | | <div id="floatlayer" style="width:50%;background:#d0d0ff;border:solid black 1px;padding:5px"> |
| | | | |
| Line 69: |
Line 65: |
| | <input type="button" value="Press Me" onclick="detach()"/> | | <input type="button" value="Press Me" onclick="detach()"/> |
| | </p> | | </p> |
| - |
| |
| | | | |
| | <p> | | <p> |
| - | Interesting effects and functionality can be achieved on Web pages by the use of floating content, or layers. By floating I mean content that moves about the page, and that does not appear in a fixed location with respect to the page layout. The content may move to follow window scrolling such that it is always visible in the window for example.
| + | <div class="example"> |
| - | | + | <div> |
| - | Imagine how handy this type of functionality could be when displaying a large number of rows in a table when a series of buttons need to be provided for actioning the selection of some rows. Without a scroll sensitive floating button-bar, the table would either require button duplication in amongst the rows, duplication of the buttons at the top and bottom, or a bunch of frames to allow the user to easily select some rows and action them. With the floating controls, the user could scroll away, selecting rows as required, then simply action them using constantly in-view buttons.
| + | |
| - | | + | |
| - | Calling this floating content a layer, although semantically and conceptually convenient, is not quite right. Layers as such do not exist in Web pages. Netscape used to have a <layer> tag that provided much of the same functionality, but today this does not exist. Instead, floating content is achieved with the use of position controlled <div >s. However, we shall still refer to the floating content as a layer for the sake of convenience. | + | |
| - | | + | |
| - | With the advent of Cascading Style Sheets (CSS) and the integration of the Document Object Model (DOM) into JavaScript, the positioning and control of <div>s has become an everyday task. Interesting effects and functionality can be achieved on Web pages by the use of floating content, or layers. By floating I mean content that moves about the page, and that does not appear in a fixed location with respect to the page layout. The content may move to follow window scrolling such that it is always visible in the window for example.
| + | |
| - | | + | |
| - | Imagine how handy this type of functionality could be when displaying a large number of rows in a table when a series of buttons need to be provided for actioning the selection of some rows. Without a scroll sensitive floating button-bar, the table would either require button duplication in amongst the rows, duplication of the buttons at the top and bottom, or a bunch of frames to allow the user to easily select some rows and action them. With the floating controls, the user could scroll away, selecting rows as required, then simply action them using constantly in-view buttons.
| + | |
| - | | + | |
| - | Calling this floating content a layer, although semantically and conceptually convenient, is not quite right. Layers as such do not exist in Web pages. Netscape used to have a <layer> tag that provided much of the same functionality, but today this does not exist. Instead, floating content is achieved with the use of position controlled <div>s. However, we shall still refer to the floating content as a layer for the sake of convenience.
| + | |
| - | | + | |
| - | With the advent of Cascading Style Sheets (CSS) and the integration of the Document Object Model (DOM) into JavaScript, the positioning and control of <div>s has become an everyday task. Interesting effects and functionality can be achieved on Web pages by the use of floating content, or layers. By floating I mean content that moves about the page, and that does not appear in a fixed location with respect to the page layout. The content may move to follow window scrolling such that it is always visible in the window for example.
| + | |
| - | | + | |
| - | Imagine how handy this type of functionality could be when displaying a large number of rows in a table when a series of buttons need to be provided for actioning the selection of some rows. Without a scroll sensitive floating button-bar, the table would either require button duplication in amongst the rows, duplication of the buttons at the top and bottom, or a bunch of frames to allow the user to easily select some rows and action them. With the floating controls, the user could scroll away, selecting rows as required, then simply action them using constantly in-view buttons.
| + | |
| - | | + | |
| - | Calling this floating content a layer, although semantically and conceptually convenient, is not quite right. Layers as such do not exist in Web pages. Netscape used to have a <layer> tag that provided much of the same functionality, but today this does not exist. Instead, floating content is achieved with the use of position controlled <div> s. However, we shall still refer to the floating content as a layer for the sake of convenience. | + | |
| | | | |
| - | With the advent of Cascading Style Sheets (CSS) and the integration of the Document Object Model (DOM) into JavaScript, the positioning and control of <div> s has become an everyday task. | + | </div> |
| | + | </div> |
| | </p> | | </p> |
| | | | |
"
