vertical split pane workaround for IE

Alex Russell <[email protected]>
Newsgroups gmane.comp.windows.devel.netwindows
Organization netWindows.org
Message-ID <[email protected]>
Ok, this is going to make everyone groan (myself included), but it seems the 
"problem" with the veritical split pane under IE is related to the document's 
doctype.

The standards-compliant way of doing things is never to calcuate height 
relative to view-pane size, but rather the calculated height of all of the 
content on the page, irregardless of the view pane's size. This means that if 
there's a thousand-pixel-high image on the page, a height: 100%; CSS value 
will translate into 1000px irrespective of whether or not the browser can 
display more or less than this in a single "page".

The old (broken) behavior instead pegged height to the viewport, and this is I 
think what we're all looking for when using the split pane as a full-page 
vertical splitter. To get this, we need to use the "fixed" position type 
which once again allows us to tag things to the viewport (at least in screen 
media, print is a different story).

To make your full-screeen vertically split pages "place nice" again, declare 
your body tag something like:

<body style="height: 100%; position: fixed;">
  <div nwType="split_pane" vertical="true" ... >
    ...
  </div>
</body>

The net effect here is to make the viewpane fill the viewport and then to fill 
the viewpane with our widget. This is working for me on both IE 6.0 under a 
standards-mode DTD as well as Moz on the same page. See the updated 
full_page_split_pane.html example for details.

HTH.

-- 
Alex Russell
[email protected]    BD10 7AFC 87F6 63F9 1691 83FA 9884 3A15 AFC9 61B7
[email protected]  F687 1964 1EF6 453E 9BD0 5148 A15D 1D43 AB92 9A46

_______________________________________________
The netWindows developers list: [email protected]
http://netwindows.org/mailman/listinfo/devel_netwindows.org
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.