<div dir="ltr">On Thu, Aug 28, 2008 at 11:11 AM, Kristof Zelechovski <span dir="ltr"><<a href="mailto:giecrilj@stegny.2a.pl">giecrilj@stegny.2a.pl</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
"javascript:goBack();" is a labeled statement in JavaScript and the label is<br>
"javascript". What purpose does it serve in your inline code?<br>
SCRIPT[type="text/xml"] can be used for semantics, including RDF.<br>
Inline styles and inline event handlers belong to deprecated legacy syntax.<br>
Inline styles were more deprecated than inline event handlers, to the point<br>
of banning them altogether. Anyway, another inline intruder should not<br>
expect a warm reception.</blockquote><div><br>Of course, now @style is a global attribute.<br> <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
You can replace [style] with [class], thereby moving the style to an<br>
external resource, but shortening the code in [onevent] does not make it any<br>
better. There is no external declarative way of attaching event handlers to<br>
elements, except in Microsoft Internet Explorer where you can have CSS<br>
behaviors and SCRIPT[for] (and FUNCTION ID_ONEVENT in Visual Basic Scripting<br>
Edition), but these are proprietary extensions.<br></blockquote></div><br>Not quite declarative, but I fail to see how that's a necessity. You can get pretty darn close, though, with any decent getElementsBySelector function (I use one created by Dean Edwards that works wonderfully for adding show/hide functionality to some of my pages).<br>
<br><span class="HcCDpe"><span class="EP8xU" style="color: rgb(121, 6, 25);">Ben Adida</span> <span class="lDACoc"><<a href="mailto:ben@adida.net">ben@adida.net</a>> said:</span></span><br><blockquote>Well, that was the argument some made, but it was soundly rejected by<br>
folks who felt we were stepping on @class's toes. At the end of the day,<br>
we went with the least amount of disruption possible.<br></blockquote><br>Those folks must *really* hate microformats, then, as they pack *all* of their semantics into @class.<br><br>~TJ<br></div>