[prev in list] [next in list] [prev in thread] [next in thread]
List: tapestry-dev
Subject: [jira] [Closed] (TAP5-2230) AjaxFormLoop Add Row Broken
From: "Thiago H. de Paula Figueiredo (JIRA)" <jira () apache ! org>
Date: 2014-01-26 20:13:40
Message-ID: JIRA.12680308.1384960786702.16012.1390767220666 () arcas
[Download RAW message or body]
[ https://issues.apache.org/jira/browse/TAP5-2230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel \
]
Thiago H. de Paula Figueiredo closed TAP5-2230.
-----------------------------------------------
> AjaxFormLoop Add Row Broken
> ---------------------------
>
> Key: TAP5-2230
> URL: https://issues.apache.org/jira/browse/TAP5-2230
> Project: Tapestry 5
> Issue Type: Bug
> Affects Versions: 5.4
> Reporter: Peter H
> Assignee: Thiago H. de Paula Figueiredo
> Labels: month-of-tapestry
> Fix For: 5.4
>
>
> We're using 5.4.26 but have seen this in 5.4.25 too so assume it's a fairly \
> long-standing issue in the alphas. Use ajaxformloop, click add row, check your \
> browser's console, see client-side error as follows: Uncaught TypeError: Object \
> <DIV class="trowandloadsmoremarkupbesidesthatistheentirecontentsofyourajaxformloop</DIV> \
> has no method 'trigger' Look at ajaxformloop.js, see lines 42-44.
> newElement = "<" + insertionPoint.element.tagName + " class=\"" + \
> insertionPoint.element.className + "\"\n data-container-type=\"" + FRAGMENT_TYPE + \
> "\">\n " + content + "\n </" + insertionPoint.element.tagName + ">"; \
> insertionPoint.insertBefore(newElement); return \
> newElement.trigger(events.zone.didUpdate); Change them to the following:
> {code}
> newElement = "<" + insertionPoint.element.tagName + " class=\"" + \
> insertionPoint.element.className + "\"\n data-container-type=\"" + FRAGMENT_TYPE + \
> "\">\n " + content + "\n </" + insertionPoint.element.tagName + ">"; newElement = \
> insertionPoint.insertBefore(newElement); return \
> newElement.trigger(events.zone.didUpdate); {code}
> Note the missing assignment of the newElement after its insertion. We are calling \
> trigger on a string. And all is fixed. :D
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic