[tw.dynforms] #8: Form encode modified values in hiding*List fields do not cause onchange to be run

0 views
Skip to first unread message

Trac from toscawidgets.org

unread,
Jul 18, 2008, 2:46:12 PM7/18/08
to toscawidge...@groups.google.com
#8: Form encode modified values in hiding*List fields do not cause onchange to
be run
------------------------+---------------------------------------------------
Reporter: jtate | Owner: somebody
Type: defect | Status: new
Priority: major | Milestone:
Component: component1 | Version:
Keywords: |
------------------------+---------------------------------------------------
If something modifies the value of the checkbox or radio button between
the call to process_hiding, and the loading of the page, the form list
will appear in the incorrect hiding state.

For example, if you set the value to the non-default state in Firefox 3,
and then reload the page from cache, firefox will remember which fields
you had selected, but the page will be reset to the default hiding state.

This can also happen if you have validation errors in your form, and
formencode prepopulates your form values.

Instead of doing process_hiding on the backend, these widgets should cause
that the twd_hiding_listitem_onchange javascript method is called on page
load.

--
Ticket URL: <http://toscawidgets.org/trac/tw.dynforms/ticket/8>
tw.dynforms </trac/tw.dynforms>
tw.dynforms

Trac from toscawidgets.org

unread,
Jul 24, 2008, 8:40:14 AM7/24/08
to toscawidge...@groups.google.com
#8: Form encode modified values in hiding*List fields do not cause onchange to
be run
-------------------------+--------------------------------------------------
Reporter: jtate | Owner: paj
Type: defect | Status: accepted
Priority: major | Milestone:
Component: component1 | Version:
Resolution: | Keywords:
-------------------------+--------------------------------------------------
Changes (by paj):

* owner: somebody => paj
* status: new => accepted


Comment:

Interestingly, hiding originally worked purely on the client. I put in the
server-side processing to avoid flicker during loading. Definitely want to
keep the server-side stuff, but I guess we could have client-side onload
as well. I'll take a look...

--
Ticket URL: <http://toscawidgets.org/trac/tw.dynforms/ticket/8#comment:1>
tw.dynforms </trac/tw.dynforms>
tw.dynforms

Trac from toscawidgets.org

unread,
Jun 30, 2009, 11:02:47 PM6/30/09
to toscawidge...@groups.google.com
#8: Form encode modified values in hiding*List fields do not cause onchange to
be run
----------------------+-----------------------------------------------------
Reporter: jtate | Owner: paj
Type: defect | Status: accepted
Priority: major | Milestone:
Component: dynforms | Version:
Keywords: |
----------------------+-----------------------------------------------------
Changes (by paj):

* component: component1 => dynforms


Comment:

I believe this is fixed in tw2.dynforms, not 100% sure

--
Ticket URL: <http://toscawidgets.org/trac/tw.dynforms/ticket/8#comment:2>
tw.dynforms </trac/tw.dynforms>
tw.dynforms

Reply all
Reply to author
Forward
0 new messages