| Summary | Horde_Form_Assign broken |
| Queue | Horde Framework Packages |
| Queue Version | HEAD |
| Type | Bug |
| State | Not A Bug |
| Priority | 2. Medium |
| Owners | |
| Requester | pub (at) perseguers (dot) ch |
| Created | 07/07/2006 (6997 days ago) |
| Due | |
| Updated | 07/10/2006 (6994 days ago) |
| Assigned | |
| Resolved | 07/10/2006 (6994 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
State ⇒ Not A Bug
re-open it if necessary. And putting back the eval statements is not
an appropriate fix _if_ there's something broken. Please say how the
existing code is broken for you, and if you've updated everything or
just that file.
State ⇒ Unconfirmed
Priority ⇒ 2. Medium
Type ⇒ Bug
Summary ⇒ Horde_Form_Assign broken
Queue ⇒ Horde Framework Packages
New Attachment: fix_form_assign.patch
Bug #3740is fixed. I hadproblem for weeks using the form assign component. I tracked down the
bug up to form_assign.js and compared it with an old Horde release
(many months ago) to see that code such as (current code)
document[name + '__right'][0].selected = false;
always returned null as of old code
eval('document.' + name + '__right][0]').selected = false;
worked well.
Enclosed is a patch that fix this bug and put back the old working code.