Z
zz
Sorry for posting this here but unfortunatly I couldn't find any appropriate
newsgroup for this and since I've been active here with .net question I
figured you guys might be able to help.
This is a link to a very simple page that contains 2 DIV statements:
http://xsinx.no-ip.com:8880/TestEmbedDiv.html
One of them is embeded in the other. There is some clipping involved (the
red layer is smaller than the yellow one). If you look at the print preview
in Internet Explorer 6, you can see the red layer but not the yellow one.
It's just a very basic example to demonstrate a problem we have.
Our "real" project involves generating web pages with multiple objects (ex:
images, videos, etc) which are each contained in their own layer which are
in turn all included in one big layer which controls clipping of those
objects. Needless to say, when we use print preview in our project, nothing
appears, we only get blank pages (the clipping layer is empty, except for
the other DIVs).
Anyone knows a work around to this problem, or can confirm it's a bug?
Any comment/suggestion is welcomed at this point, I'm lost.
Thanks,
Alex.
newsgroup for this and since I've been active here with .net question I
figured you guys might be able to help.
This is a link to a very simple page that contains 2 DIV statements:
http://xsinx.no-ip.com:8880/TestEmbedDiv.html
One of them is embeded in the other. There is some clipping involved (the
red layer is smaller than the yellow one). If you look at the print preview
in Internet Explorer 6, you can see the red layer but not the yellow one.
It's just a very basic example to demonstrate a problem we have.
Our "real" project involves generating web pages with multiple objects (ex:
images, videos, etc) which are each contained in their own layer which are
in turn all included in one big layer which controls clipping of those
objects. Needless to say, when we use print preview in our project, nothing
appears, we only get blank pages (the clipping layer is empty, except for
the other DIVs).
Anyone knows a work around to this problem, or can confirm it's a bug?
Any comment/suggestion is welcomed at this point, I'm lost.
Thanks,
Alex.