<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"Segoe UI";
panose-1:2 11 5 2 4 2 4 2 2 3;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";
color:black;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body bgcolor=white lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>I would personally prefer to stay away from the path that makes
Seaside browser/design-aware, which is what you’re suggesting, its just
not Seaside’s job. Instead the person designing your CSS (even if its
yourself) should handle browser differences there, for example by including an
extra CSS for IE’s consumption, which is what we do for our site,<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>/* IE6/Win-specific CSS */<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>@import url("ie6win.css");<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Hope this helps,<o:p></o:p></span></p>
<div>
<p><span style='font-size:10.0pt;color:#1F497D'>-Boris<br>
<br>
--<br>
+1.604.689.0322<br>
DeepCove Labs Ltd.<br>
4th floor 595 Howe Street<br>
Vancouver, Canada V6C 2T5<br>
<br>
boris@deepcovelabs.com<br>
<br>
CONFIDENTIALITY NOTICE<br>
<br>
This email is intended only for the persons named in the message<br>
header. Unless otherwise indicated, it contains information that is<br>
private and confidential. If you have received it in error, please<br>
notify the sender and delete the entire message including any<br>
attachments.<br>
<br>
Thank you.</span><o:p></o:p></p>
</div>
<div>
<div style='border:none;border-top:solid #91C0FF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal style='margin-left:.5in'><b><span style='font-size:9.0pt;
font-family:"Segoe UI","sans-serif";color:windowtext'>From:</span></b><span
style='font-size:9.0pt;font-family:"Segoe UI","sans-serif";color:windowtext'>
seaside-bounces@lists.squeakfoundation.org
[mailto:seaside-bounces@lists.squeakfoundation.org] <b>On Behalf Of </b>Rick
Flower<br>
<b>Sent:</b> Thursday, November 02, 2006 10:42 AM<br>
<b>To:</b> The Squeak Enterprise Aubergines Server - general discussion.<br>
<b>Subject:</b> [Seaside] Self adjusting CSS (based on browser type) extension
toSeaside?<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p>
<p class=MsoNormal style='margin-left:.5in'>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...?<o:p></o:p></p>
</div>
</body>
</html>