No I totally appreciate updating documentation of all things....So don't let me deter you from making changes. I don't think I've told anyone about those changes as they seemed like steps involved in fixing an outright bug. (hopefully it'll show itself again so I can attack it)
On 6/26/07, Marcus Schulte <[EMAIL PROTECTED]> wrote:
Huh, I'll double-check, whether this was my fault. I know, I was fighting with that one 10 days or so ago - but who knows what I messed up jar-wise. I'll check tomorrow and tell you. 2007/6/26, Jesse Kuhnert <[EMAIL PROTECTED]>: > > Hmm....I wonder if this is really still true? I've gone through great > pains > to ensure that both the body and the actual dom element are replaced for > IE > specifically so am slightly concerned if this is not the case. > > I do know this was true for earlier versions of 4.1 (and possibly even > 4.1.1or the starting point of > 4.1.2) and definitely true in Tacos but should not be true today. > > Either way I guess if you know of a use case I can look at I"d love to get > this fixed in 4.1.3 if there is anything I've missed. There is no excuse > for me to not have it work as intended. > > On 6/26/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > > > Author: mschulte > > Date: Tue Jun 26 13:21:12 2007 > > New Revision: 550930 > > > > URL: http://svn.apache.org/viewvc?view=rev&rev=550930 > > Log: > > document behaviour described in TAPESTRY-1580 > > > > Modified: > > tapestry/tapestry4/trunk/src/site/apt/ajax/responsebuilder.apt > > > > Modified: tapestry/tapestry4/trunk/src/site/apt/ajax/responsebuilder.apt > > URL: > > > http://svn.apache.org/viewvc/tapestry/tapestry4/trunk/src/site/apt/ajax/responsebuilder.apt?view=diff&rev=550930&r1=550929&r2=550930 > > > > > ============================================================================== > > --- tapestry/tapestry4/trunk/src/site/apt/ajax/responsebuilder.apt > > (original) > > +++ tapestry/tapestry4/trunk/src/site/apt/ajax/responsebuilder.apt Tue > Jun > > 26 13:21:12 2007 > > @@ -50,7 +50,29 @@ > > +----------------------------------------------------------------------- > > > > The string value passed in to <<<updateComponent(String > componentId)>>> > > is the component id of the component > > - you would like to update. > > + the body of which you would like to update. > > > > Tapestry will correctly manage and render all javascript/form > state/etc > > needed, depending on the component > > type you are requesting an update on. > > + > > + Note, that some Browsers (most notably, Internet Explorer) require > the > > updated body to consist of a single > > + element. Thus, in your template, instead of > > + > > > > > ++------------------------------------------------------------------------- > > + <span jwcid="[EMAIL PROTECTED]"> > > + <span jwcid="@Insert" value="ognl:project.lead.name" > class="nameClas" > > /> > > + <span jwcid="@Insert" value="ognl:project.lead.email" > > class="mailClass" /> > > + </span> > > > > > ++-------------------------------------------------------------------------- > > + > > + you should rather have: > > + > > > > > ++------------------------------------------------------------------------- > > + <span jwcid="[EMAIL PROTECTED]"> > > + <span> > > + <span jwcid="@Insert" value="ognl:project.lead.name" > > class="nameClas" /> > > + <span jwcid="@Insert" value="ognl:project.lead.email" > > class="mailClass" /> > > + </span> > > + </span> > > > > > ++-------------------------------------------------------------------------- > > + > > > > > > > > > -- > Jesse Kuhnert > Tapestry/Dojo team member/developer > > Open source based consulting work centered around > dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com > -- Marcus Schulte http://marcus-schulte.blogspot.com
-- Jesse Kuhnert Tapestry/Dojo team member/developer Open source based consulting work centered around dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
