<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=utf-8">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7651.59">
<TITLE>Re: [Seaside] [2.8] WAAnchorTag>>onClick:</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>Fair enough, I do expect to find things and that's why I'm doing it. Whatever you decide to do I think its important to have href added automagically to anchors that are there for onclick alone so that anchor styling applied still. No?<BR>
<BR>
Cheers!<BR>
<BR>
-Boris<BR>
(Sent from an iPhone... Not!)<BR>
<BR>
----- Original Message -----<BR>
From: seaside-bounces@lists.squeakfoundation.org <seaside-bounces@lists.squeakfoundation.org><BR>
To: Seaside - general discussion <seaside@lists.squeakfoundation.org><BR>
Sent: Sat Jul 07 02:27:05 2007<BR>
Subject: Re: [Seaside] [2.8] WAAnchorTag>>onClick:<BR>
<BR>
> This one took almost 20 minutes to track down. Previous version stuffed<BR>
> 'javascript:void(0)' into href-less anchors to make browsers respect it<BR>
> as an anchor and apply styles, whereas 2.8 is not doing it anymore. What<BR>
> was the reason for removal?<BR>
<BR>
Note that Seaside 2.8 is still work in progress and that you just<BR>
discovered a place where refactorings are going on.<BR>
<BR>
The initial reason for this change was WAPopupAnchorTag:<BR>
<BR>
1. WAPopupAnchorTag produced invalid Javascript up to know.<BR>
<BR>
2. The recent refactoring enables:<BR>
- Search engines follow the link.<BR>
- Anchors work even if Javascript is disabled.<BR>
- Power user have a better control where the new window should be<BR>
opened (same window, new window, new tab).<BR>
<BR>
3. Moreover the refactoring made WAPopupAnchorTag a real subtype of<BR>
WAAnchorTag, before it was just a hack that added some behavior of<BR>
WAAnchorTag but mostly destroyed functionality from its superclass.<BR>
<BR>
4. Less code. Less magic.<BR>
<BR>
This refactoring would not have been possible, if WAAnchorTag<BR>
automatically added javascript:void(0) to the on click event.<BR>
<BR>
We are about to clean up WAAnchorTag (in a backward compatible way).<BR>
Some general ideas that drive these cleanups of the tag hierarchy are:<BR>
<BR>
1. Dependencies in the order of configuration messages should be<BR>
avoided altogether (this was not the case with #onClick:). The only<BR>
thing people should need to know is that #with: has to be last.<BR>
<BR>
2. Configuration messages should not have unpredictable side-effects<BR>
(again this was not the case with #onClick:).<BR>
<BR>
3. URLs should be URL objects, not Strings. Only this allows to<BR>
properly encode the resulting response.<BR>
<BR>
Lukas<BR>
<BR>
--<BR>
Lukas Renggli<BR>
<A HREF="http://www.lukas-renggli.ch">http://www.lukas-renggli.ch</A><BR>
_______________________________________________<BR>
Seaside mailing list<BR>
Seaside@lists.squeakfoundation.org<BR>
<A HREF="http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside">http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside</A><BR>
</FONT>
</P>
</BODY>
</HTML>