N
Neo Geshel
I'm helping on a web site, and it's got our knickers in a knot. We're
using the same basic CSS files (with mods) and same headers as from our
other sites, but the "print preview" won't work correctly on this site.
The site is here: http://askdrray.kabis.net (temporary location)
The site is being worked on, and only the front page works right now.
Expect constant changes. Ignore everything “below the foldâ€, as the
links there are not correct yet.
The CSS is broken up into four main files: a general one, for
device-independent CSS, one for Screen, one for Mobile devices (phones,
pda's) and one for printing.
For some strange reason, IE doesn't want to follow or even obey the
instructions inside the print css file. Many elements that should be
gone in the print version still appear. Why? Everything works fine in
Mozilla/Firefox - use that to see things as it should appear.
In order to flag elements in a very customizable way, we have created
six classes that exist in each of the three secondary files: printshow,
printhide, screenshow, screenhide, handshow handhide. Each class in each
css file contains code that will "handle" any element in the right way
for that particular case. For example, the print.css file would normally
have something like this:
.printhide { display: none; }
.screenshow { display: none; }
.printshow { display: inline;}
and yet IE still displays the elements that have class="printhide" or
class="screenshow" in a print preview or in a print output, when in fact
it should not. This is where we are scratching out heads. We must me
missing something really simple and stupid.
Also, a quick accessibility check (with Jaws) would be appreciated. How
does the site work for the disabled??
TIA
...Geshel
--
**********************************************************************
My reply-to is an automatically monitored spam honeypot. Do not use it
unless you want to be blacklisted by SpamCop. Please reply to my first
name at my last name dot org.
**********************************************************************
using the same basic CSS files (with mods) and same headers as from our
other sites, but the "print preview" won't work correctly on this site.
The site is here: http://askdrray.kabis.net (temporary location)
The site is being worked on, and only the front page works right now.
Expect constant changes. Ignore everything “below the foldâ€, as the
links there are not correct yet.
The CSS is broken up into four main files: a general one, for
device-independent CSS, one for Screen, one for Mobile devices (phones,
pda's) and one for printing.
For some strange reason, IE doesn't want to follow or even obey the
instructions inside the print css file. Many elements that should be
gone in the print version still appear. Why? Everything works fine in
Mozilla/Firefox - use that to see things as it should appear.
In order to flag elements in a very customizable way, we have created
six classes that exist in each of the three secondary files: printshow,
printhide, screenshow, screenhide, handshow handhide. Each class in each
css file contains code that will "handle" any element in the right way
for that particular case. For example, the print.css file would normally
have something like this:
.printhide { display: none; }
.screenshow { display: none; }
.printshow { display: inline;}
and yet IE still displays the elements that have class="printhide" or
class="screenshow" in a print preview or in a print output, when in fact
it should not. This is where we are scratching out heads. We must me
missing something really simple and stupid.
Also, a quick accessibility check (with Jaws) would be appreciated. How
does the site work for the disabled??
TIA
...Geshel
--
**********************************************************************
My reply-to is an automatically monitored spam honeypot. Do not use it
unless you want to be blacklisted by SpamCop. Please reply to my first
name at my last name dot org.
**********************************************************************