Details
Improvement
Major
Description
After a page is initially loaded, the first Ajax request will trigger a larger than necessary update due to the changing ViewState values in the hidden input fields. This will typically mean that the full form is always sent back as the first update.
Issue Links
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
Full form updates caused by this issue mask the updates that are calculated by h:message and h:messages rendering.
Show
Deryk Sinotte
added a comment - Full form updates caused by this issue mask the updates that are calculated by h:message and h:messages rendering.
I modified the DOMResponseWriter to use a similar strategy to what we do with Mojarra. That is, when MyFaces adds the ViewState elements, we identify it and store it for later removal. We allow the response to be written back (including all the ViewState elements) and then remove them from the DOM after. This way, they are not in the DOM when a DOM diff is done and don't trigger the larger updates.
Show
Deryk Sinotte
added a comment - I modified the DOMResponseWriter to use a similar strategy to what we do with Mojarra. That is, when MyFaces adds the ViewState elements, we identify it and store it for later removal. We allow the response to be written back (including all the ViewState elements) and then remove them from the DOM after. This way, they are not in the DOM when a DOM diff is done and don't trigger the larger updates.
Linking to the MyFaces 2 parent JIRA for general compatibility. While it doesn't technically fail (and therefore doesn't actually block MyFaces compatibility), the large initial update is not optimal.