-- Andreas Joseph Krogh <and...@officenet.no> - mob: +47 909 56 963 Senior Software Developer / CTO - OfficeNet AS - http://www.officenet.no Public key: http://home.officenet.no/~andreak/public_key.asc
My guess is, it's the different life cycles of RequestVars
The onBlur is an ajax request so it uses the same RequestVars as was on
the original page but the submit is a different request and gets new
values.
Oh wait the submit is also ajax...hmm so much for that theory :-)
Could be though, that the submit is still considered
"different"...haven't looked at the code.
/Jeppe
Exactly:-)
> Could be though, that the submit is still considered
> "different"...haven't looked at the code.
By the way RequestVars are advertised this should work if I'm not mistaken... The strange thing is that this behavior goes way back and is not new (I've tested with 2.3 and different scala-versions).
The strange thing is that I experienced it working once or twice but am not able to reproduce.
Could be though, that the submit is still considered
"different"...haven't looked at the code.
Yes, I call this the "assignmentCallback" (because it's often in this callback you assign the input to something). For various reasons I need to access a request-var in this callback so it's a blocker for me.
--
Lift, the simply functional web framework: http://liftweb.net
Code: http://github.com/lift
Discussion: http://groups.google.com/group/liftweb
Stuck? Help us help you: https://www.assembla.com/wiki/show/liftweb/Posting_example_code
From what I can see there are no more critical issues in 2.4-SNAPSHOT so
getting 2.4 released seems pretty ok by me. Would be better for that
AJAX-overhaul to make it into 2.5 I think. That doesn't mean it's less
important tho...
On 11/28/2011 06:06 PM, David Pollak wrote:From what I can see there are no more critical issues in 2.4-SNAPSHOT so
> Yes... it's 980. Each of the Ajax callbacks perform an explicit
> RequestVar restore to give you the same environment. The onEvent
> doesn't do the RenderVar restore. This will all be fixed when I get
> to 980.
>
> As a process issue, we're in semi code slush per Indrajit's latest
> note. If I tackle 980, it will be a major change to how Lift handles
> Ajax and should be done with lots of heads up to developers. What's
> the thought on another 2.4 milestone versus getting 980 into 2.5?
getting 2.4 released seems pretty ok by me.
Would be better for that
AJAX-overhaul to make it into 2.5 I think. That doesn't mean it's less
important tho...
--
Andreas Joseph Krogh <and...@officenet.no> - mob: +47 909 56 963
Senior Software Developer / CTO - OfficeNet AS - http://www.officenet.no
Public key: http://home.officenet.no/~andreak/public_key.asc
--
Lift, the simply functional web framework: http://liftweb.net
Code: http://github.com/lift
Discussion: http://groups.google.com/group/liftweb
Stuck? Help us help you: https://www.assembla.com/wiki/show/liftweb/Posting_example_code
> On Mon, Nov 28, 2011 at 11:04 AM, Andreas Joseph Krogh <and...@officenet.no
>> wrote:
>
>> On 11/28/2011 06:06 PM, David Pollak wrote:
>> > Yes... it's 980. Each of the Ajax callbacks perform an explicit
>> > RequestVar restore to give you the same environment. The onEvent
>> > doesn't do the RenderVar restore. This will all be fixed when I get
>> > to 980.
>> >
>> > As a process issue, we're in semi code slush per Indrajit's latest
>> > note. If I tackle 980, it will be a major change to how Lift handles
>> > Ajax and should be done with lots of heads up to developers. What's
>> > the thought on another 2.4 milestone versus getting 980 into 2.5?
>>
>> From what I can see there are no more critical issues in 2.4-SNAPSHOT so
>> getting 2.4 released seems pretty ok by me.
>
>
> It'd be great to have a prioritized list of 2.4 release-blocking issues.
> Anyone want to chime in?
There are no tickets left for the 2.4 milestone (there is no 2.4
milestone :-)
I just browsed the tickets in "No milestone" and nothing there seems to
be a blocker....so unless someone speaks up and points to a blocking
ticket, I guess there are none.
/Jeppe
I don't want to resurrect an old thread, but I think this issue just bit me for a few hours this evening.The basic scenario is almost identical to the original poster, except I'm using:
".selector [onchange]" #> SHtml.onEvent(_ => Set some variable)I've been able to work around it using snippet class variables (or locally scoped variables with closure), but I was hoping to be able to set some information in a requestVar and have multiple snippets update and reference it via ajax callbacks. (in which case I can't just use a snippet class variable.) Is there another pattern in lift for sharing information across snippets?
--
--
Lift, the simply functional web framework: http://liftweb.net
Code: http://github.com/lift
Discussion: http://groups.google.com/group/liftweb
Stuck? Help us help you: https://www.assembla.com/wiki/show/liftweb/Posting_example_code