[Seaside-dev] Issue 106 in seaside: Checkbox with no callback triggers an error

[codesite-noreply at google.com]

Issue 106: Checkbox with no callback triggers an error
http://code.google.com/p/seaside/issues/detail?id=106

Comment #1 by jfitzell:
Fixed.

Name: Seaside-Core-jf.178
Author: jf
Time: 20 July 2008, 10:00:01 am
UUID: aa7ad8fb-d2c0-484e-957d-3316540dd581
Ancestors: Seaside-Core-pmm.177

Fix http://code.google.com/p/seaside/issues/detail?id=106 by not 
outputting the
hidden input tag for a checkbox if there is no callback. This seems semantically
correct to me: if there's no callback on the checkbox tag itself, why 
have the hidden
tag at all.

If anyone prefers, the hidden tag could still be generated and the 
callback could
contain the conditional check to see whether to call the real callback, 
but I don't
see a need.


Name: Seaside-Tests-jf.135
Author: jf
Time: 20 July 2008, 10:02:58 am
UUID: 2d0fd0a7-811b-d448-9f9c-8007fd96628e
Ancestors: Seaside-Tests-jf.134

Adjust tests based on changes in Seaside-Core-jf.178 and in response to
http://code.google.com/p/seaside/issues/detail?id=106

The theory is that, if the checkbox has no callback, the hidden input 
tag is not needed.


I can't write a proper unit test for this... see issue 107


Issue attribute updates:
	Status: Fixed

-- 
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings