<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
I just tested an app I've been working on (tested mostly in Safari
& Firefox which look fine) but this time tried it on IE6 and it
looks really bad -- mostly due to font differences (fonts are huge
which are causing wrapping) which I've yet to account for in my
existing CSS.. It got me to thinking about ways to have some sort of
system in Seaside were you could specify portable font sizes or types
(and whatever else) in your CSS style methods that Seaside could then
translate into the proper actual CSS code on-the-fly for the specific
browser being used.. What I'm thinking is that you could have CSS that
looks something like that shown below in the before/after code :<br>
<br>
<b><u>Before Modification</u></b> (e.g. plain old CSS)<br>
<br>
div#byitem ul.vert <br>
{<br>
list-style-type: none;<br>
padding: 0;<br>
margin: 0;<br>
width: 640px;<br>
font-size: 9pt;<br>
font-family: "Courier New", Courier, Arial, sans-serif,
monospace;<br>
}<br>
<br>
<b><u>After Modification</u></b><br>
<br>
div#byitem ul.vert <br>
{<br>
list-style-type: none;<br>
padding: 0;<br>
margin: 0;<br>
width: 640px;<br>
@font-size: 9pt;<br>
@font-family: monospace;<br>
}<br>
<br>
This way, some new code in Seaside could see that you're using IE 6
(for instance -- perhaps IE7 behaves different) and modify the
font-size and font-family accordingly to make something that works
better for IE -- e.g. tailoring if you will. Right now, there's no
clean way aside from doing ugly css hacks to get IE to do what you want
without breaking the formatting for Firefox/Safari,etc.. This way is
more programmatic and you could have a collection of substitutions
based on browser type and keyword or something along those lines.. The
nice thing about such a mechanism is that you could totally skip it if
you didn't want to use it.. Perhaps this is just not needed as there
are so many browser quirks out there -- Anyway, not sure if anyone has
any comments on whether this sounds interesting or not...?<br>
</body>
</html>