Michael Adams wrote:
However, my personal preference is for the @import hack:
FOR
* The CSS stays in the css files (doesn't cause you to hack the header)
* Create code for the standards compliant browsers then hack for IE
* All IE hacks are in a seperate file
* It may not need to work
Michael Adams wrote
I have been lurking here for the last month and have a question about
the right way to handle IE using CSS.
I use a master CSS file with the format as follows. To me, the master
file method as well as solving the 'old browser' issue, is easier for
another designer to
I have a question related to the same issue.
I am converting a very poorly constructed table based site to CSS.
It is a tight fixed width site. Since it is a child of a larger site,
I don't feel I can convert to a more fluid site or change the look and
feel.
I have used
/*** IE Fix ***/
* html
Nancy Johnson wrote: I have a question related to the same issue. I am
converting a very poorly constructed table based site to CSS. It is a tight
fixed width site. Since it is a child of a larger site, I don't feel I can
convert to a more fluid site or change the look and feel. I have used
Please let me apologize for my last message, my webmail time out.
Nancy Johnson wrote:
I have a question related to the same issue.
I am converting a very poorly constructed table based site to CSS.
It is a tight fixed width site. Since it is a child of a larger site,
I don't feel I can
On Wed, 09 Jan 2008 13:32:39 -0500
Nancy Johnson wrote:
[snip]
Is @import?
or
!--[if IE.xx]
link rel=stylesheet type=text/css media=screen
href=/css/IEstylesheet.css / ![endif]--
a better way?
Conditional comments are by far the safer and generally more preferred
method.
On Wed, 09 Jan 2008 04:50:22 -0700
Alan Gresley wrote:
Michael Adams wrote
I have been lurking here for the last month and have a question
about the right way to handle IE using CSS.
I use a master CSS file with the format as follows. To me, the
master file method as well as solving
