<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
On 2/12/11 8:59 PM, JoeS wrote:
<blockquote cite="mid:4D57651A.2040103@gmail.com" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
On 2/12/2011 10:24 PM, <a moz-do-not-send="true"
class="moz-txt-link-abbreviated"
href="mailto:philringnalda@gmail.com">philringnalda@gmail.com</a>
wrote:
<blockquote cite="mid:4D574EF7.6090804@gmail.com" type="cite">On
2/12/11 6:46 PM, JoeS wrote: <br>
<blockquote type="cite">It seems to me that CSS3 in most cases
requires that JS must be allowed. <br>
</blockquote>
<br>
That is not at all the case. An accurate statement would be more
like "CSS3 demos are more fun to write if you throw in some JS,
muddying just exactly what it is that you are demoing." Sure
about that Phil,<br>
</blockquote>
<font face="Arial"> Just show an example here, or to my email, and
I'll just shutup.<br>
Show me an object or image that transitions across the screen.<br>
I don't have a farm to bet, but if I did, I think I would bet
that it won't work.</font><br>
</blockquote>
<style type="text/css">
#victim {
position: absolute;
left: 0;
width: 100;
height: 100;
text-align: center;
-moz-transition-property: background-color, color, left;
-moz-transition-duration: 5s;
background-color: red;
color: black;
}
#victim:focus {
left: 80%;
background-color: blue;
color: white;
}
#container {
width: 100%;
height: 150;
}
</style>
<div id="container"><button id="victim">Hit tab until I get focus</button></div>
If you got the impression that CSS3 is the same thing as CSS3
transitions and transformations, I'm sorry you misunderstood it.
That's a tiny part of CSS3, not what it is.<br>
<br>
If you got the impression that supporting CSS3 transitions and
transformations because Gecko does meant that we somehow
automatically have to make it exactly as easy for authors to use and
trigger them in an email client as it is in a browser when that
browser happens to have JS enabled, I'm sorry you misunderstood.
Just because there are fewer ways to trigger a change in style in an
email client than there are in a browser doesn't mean that we have
to allow JS in email. I know, everyone knows, that you want to find
some magic fact that will mean that we have no choice but to allow
JS in email no matter the cost, but no such magic fact exists.<br>
</body>
</html>