Re: t5: Returning block works in Firefox but not in IE

I am using Firefox 3.0 and T 5.0.13, still has this problem. Tan [EMAIL PROTECTED] wrote: > > tapestry 5.0.13 have solved the problem on IE > > On Mon, Jun 30, 2008 at 4:14 PM, Lance Java <[EMAIL PROTECTED]> > wrote: > >> With me, I had a javascript bug so tapestry's javascript did not execute

Re: t5: Returning block works in Firefox but not in IE

tapestry 5.0.13 have solved the problem on IE On Mon, Jun 30, 2008 at 4:14 PM, Lance Java <[EMAIL PROTECTED]> wrote: > With me, I had a javascript bug so tapestry's javascript did not execute. > I fixed my javascript bugs and everything started working. > > 2008/6/30 Weisu <[EMAIL PROTECTED]>: >

Re: t5: Returning block works in Firefox but not in IE

With me, I had a javascript bug so tapestry's javascript did not execute. I fixed my javascript bugs and everything started working. 2008/6/30 Weisu <[EMAIL PROTECTED]>: > > Hi Lance, I have the same error message. Could you kindly show the steps to > make this work? > Thanks in advance. > Weisu.

Re: t5: Returning block works in Firefox but not in IE

Hi Lance, I have the same error message. Could you kindly show the steps to make this work? Thanks in advance. Weisu. Lance Java wrote: > > Yep, that's what I meant > > 2008/6/25 9902468 <[EMAIL PROTECTED]>: > >> >> Better yet: >> >> Tapestry could be so smart that it would return null even if

Re: t5: Returning block works in Firefox but not in IE

Yep, that's what I meant 2008/6/25 9902468 <[EMAIL PROTECTED]>: > > Better yet: > > Tapestry could be so smart that it would return null even if the handler > returns block if the request is not ajax. > > if(return_value == block && is_not_xhdr){ >block = null; > } > > That wouldn't break any

Re: t5: Returning block works in Firefox but not in IE

Better yet: Tapestry could be so smart that it would return null even if the handler returns block if the request is not ajax. if(return_value == block && is_not_xhdr){ block = null; } That wouldn't break anything? -99 Lance Java wrote: > > Could returning null be built in as default

Re: t5: Returning block works in Firefox but not in IE

Could returning null be built in as default behaviour? Since returning a block from a non-xhr request is an error case, it would save putting checks throughout the code and I can't see it breaking anything. Cheers, Lance. 2008/6/24 Howard Lewis Ship <[EMAIL PROTECTED]>: > For full graceful degra

Re: t5: Returning block works in Firefox but not in IE

For full graceful degradation, you can inject the Request object can check its isXHR() method, then decide on an appropriate return value (typically, a Block or null). On Tue, Jun 24, 2008 at 9:24 AM, Lance Java <[EMAIL PROTECTED]> wrote: > I have solved the issue, I think I understand what was go

Re: t5: Returning block works in Firefox but not in IE

I have solved the issue, I think I understand what was going wrong. - Tapestry first draws action links as hrefs which cause a page reload for graceful degredation - Tapestry javascript magic then goes over all ajax action links and changes them to javascript method calls - I had a javascript error

Re: t5: Returning block works in Firefox but not in IE

Hi, I am inexperienced in Tapestry, but I had east problem recently: You have like result a valid xhtml page? You can look for if you have "scripts of tapestry" inserted at the end of the page. something like this : ... type="text/javascript"> type="text/javascript"> type="text/jav

t5: Returning block works in Firefox but not in IE

2008-06-24 Thread Lance Java

I have an actionlink that returns a block and populates a zone in my page FundGraph.tml edit ... FundGraph.java @Inject private Block editorBlock; @OnEvent(value="action", component="edit") protected Object onActionFromEdit() { return editorBlock; }