Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
2.1.0-core
-
None
-
None
Description
In my case, there's a radio select which auto-submits and opens up a set of input fields. The input fields need CoreFormat scriplet, but the page fails there because of an unknown resource "TrDoubleConverter".
If I revert the five TRINIDAD-2100 commits in the version control, the problem disappears.
EDIT:
The case mentioned above did disappear with the revert, but other instances persist. Turned out the workaround for TRINIDAD-2244 fixed the problem for real and reverting TRINIDAD-2100 is not needed.
Root of the cause seems to be that when client receives the PPR response, no other parts but "<update>" is processed and other parts (such as "<extension>" and "<eval>") are ignored:
Looking at the contents of the following functions, there's no mention of anything else but "<update>" elsewhere but in "_handlePprResponse", even though Ajax version of the PPR should do the same things, as I understand it.
TrPage.prototype.sendPartialFormPost = function (actionForm, params, headerParams, event)
TrPage.prototype._requestStatusChanged = function (requestEvent)
TrPage.prototype._jsfAjaxCallback = function (data)
TrPage.prototype._handlePprResponse = function (requestEvent, document)
Attachments
Issue Links
- relates to
-
TRINIDAD-2244 PPR_OVER_JSF_AJAX and a tr:inputText mapped to a Date in a tr:panelTabbed is broken
-
- Open
-