WAIframeTag

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

WAIframeTag

Glenn Swanlund-3

WAHtmlCanvas>>iframe is a deprecated api. So does that mean WAIframTag should not be used?

 

I would like to use this to make a Windows Explorer type interface with two frames, one holding a tree directory and the other to hold the contents. I was able to make it work with Aida and would like to try it in Seaside.

 

Any pointers?

 

Regards,

Glenn


_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Reply | Threaded
Open this post in threaded view
|

Re: WAIframeTag

Lukas Renggli
> WAHtmlCanvas>>iframe is a deprecated api. So does that mean WAIframTag
> should not be used?

iframe should not be deprecated. I added by accident and it should be
fixed. If not, please ignore this warning.

> I would like to use this to make a Windows Explorer type interface with two
> frames, one holding a tree directory and the other to hold the contents.

For that you don't need an IFRAME though. Just use a DIV and set the
CSS property:

    overflow: auto

Cheers,
Lukas

--
Lukas Renggli
http://www.lukas-renggli.ch
_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Reply | Threaded
Open this post in threaded view
|

Re: WAIframeTag

Andrew99
>> I would like to use this to make a Windows Explorer type interface with two
>> frames, one holding a tree directory and the other to hold the contents.

>For that you don't need an IFRAME though. Just use a DIV and set the
>CSS property:
>
>    overflow: auto

There is a bug in IE 6 where the content inside a DIV with the overflow set to auto or scroll is displayed beyond the bounds of the DIV.  The scrollbars show up and are sized appropriately, but they are useless.  This appears to be caused by specifying the doctype, which is automatically done with Seaside.  To resolve the issue, the doctype must not be declared.

For an example, see:
http://mt-olympus.com/emmett/bug_overflow_positionrelative.php

To resolve (or avoid) this issue, the docType used in WAHtmlRoot #writeHeadOn: needs to be blank or else  you need to put the content in an iFrame to use the scrollbars.

How should this issue be avoided/resolved?